-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Triggering parentless task in new flow caused it to spawn in later cycles #6258
Comments
Not a bug! In any flow, including the original flow and "new" ones, parentless tasks continue on to future cycles by magically spawning next instances, since they have no parents to do it "on demand". If not for this you couldn't trigger a new flow that traverses the whole graph just like the original flow. We probably do need an option to not do that, which would make this more of a feature request. We have definitely discussed this before somewhere but I can't find the associated issue.
Correction: for parentless tasks, this only prevents the one future instance (the manually expired one) from running. That's by design. If a parentless task expires or fails (say) that doesn't mean other instances beyond that cycle should not run. So for the moment, you have to trigger with |
I'm not sure what the question is here, what were you trying to achieve with this trigger?
IMO, the observed behaviour is correct for Suggest ensuring that the intended use case is adequately covered by proposed interventions and closing this if it is? |
The use case I can think of is "I want to re-run a chain in a particular cycle point, it will catch up with the blocked flow 1 and flow-merge, therefore it is unexpected that the task I triggered starts running in other cycle points" |
The best match for that would be group trigger. As I understand it (I haven't had the time to go through in detail yet): cylc trigger workflow//1 # remove all tasks (and their outputs) and re-run from the start |
Reproducible Example
causes
2/compile
,3/compile
etc to spawn again.Expected Behaviour
Only
1/compile
should spawn.Additional Context
Tested and reproduced all the way back in 8.2.6
The text was updated successfully, but these errors were encountered: