cylc-flow 8.2.7
In the cylc GUI, the tree view is organized by task families, and context menus permit operations on entire families of tasks, e.g. hold trigger. However, if I use the CLI to do:
cylc hold WORKFLOW//CYCLEPOINT/FAMILY
It reports Done but no tasks are actually held.
Hi @ejhyer
The exact same goes for the CLI, actually.
The problem is, when targeting tasks by family name or glob pattern, commands like cylc hold only match tasks in the n=0 “active window” of the workflow.
At the moment, future tasks have to be targeted by individual task ID.
There are good reasons for this, and there are some scenarios where it is not a problem (e.g., a bunch of family members fail when their success is required by the workflow - they will all be retained in n=0 as incomplete tasks, and they can all be retriggered at once by family name).
However, we do plan to extend task matching beyond the active window in a future release.
Current task matching might be surprising, especially if you come from Cylc 7 (which was actually similar in this respect, but the “active window” was typically much bigger due to inefficient pre-spawning of future tasks, which tended to hide the problem).
Unfortunately it’s not really obvious how we could advertise this prominently to GUI users. We can’t clutter up context menus with screeds of text…
And note that the GUI, by default, shows the n=1 window - i.e., the active tasks plus those one graph edge out from them - which at first glance might give the impression there are active tasks in the family.