Hi Anubhav,
When using the command “lpad defuse_wflows” on workflows containing fizzled fireworks, I expect all the WAITING, READY, and FIZZLED fireworks to be defused/paused. However, only the READY and WAITING fireworks are paused. Should this be the proper behavior, as it continues to clutter the FIZZLED fireworks?
Thanks,
Eric
Typically you would just want to defuse WAITING and READY. That is - you want to keep the jobs that errored as errored and not mess with those since you know they already failed and might not want to run them again if you reignite your fireworks later. You just want to cancel eligible jobs (READY and WAITING ones). The FIZZLED ones won’t run anyway, and you lose information that they are failed by reverting them to DEFUSED and mixing them with WAITING/READY.
If you want the FIZZLED jobs to also be DEFUSED (again, you’ll lose track of which jobs errored vs which jobs simply never ran), then first call rerun on the FIZZLED jobs to bring them back to WAITING/READY. Then call the defuse_wflows command
Best
Anubhav
On Fri, Apr 27, 2018 at 10:51 AM, [email protected] wrote:
Hi Anubhav,
When using the command “lpad defuse_wflows” on workflows containing fizzled fireworks, I expect all the WAITING, READY, and FIZZLED fireworks to be defused/paused. However, only the READY and WAITING fireworks are paused. Should this be the proper behavior, as it continues to clutter the FIZZLED fireworks?
Thanks,
Eric
–
You received this message because you are subscribed to the Google Groups “fireworkflows” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/fireworkflows.
To view this discussion on the web visit https://groups.google.com/d/msgid/fireworkflows/86ed0d10-e4b5-421f-a935-e8fb18aa4034%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Best,
Anubhav