Hi @ejhyer
What is the (expected) logic driving when tasks disappear from the “active” state
We need to distinguish between active task states (submitted, running) and the active window of the workflow - i.e., the tasks that the scheduler is currently actively managing, which includes active ones plus waiting tasks that are ready to run according to the graph but held back by (e.g.) queues, runahead limit, xtriggers, or task hold.
Tasks can leave the active window if they are complete - i.e. if they finished (succeeded or failed) AND completed all of their required (as opposed to optional) outputs.
Incomplete tasks stay in the active window until dealt with, and will stall the workflow, because their incomplete status indicates something happened that the graph does not handle automatically.
The only other way a task can leave the active window is if deliberately removed by you (cylc remove). Then, you are saying to the scheduler that you don’t need that task to be completed anymore, and damn the downstream consequences.
and (thus?) disappear from the GUI?
That’s a slightly different thing. The GUI shows the tasks in the active window PLUS future and past tasks out to n (default 1) graph edges out from them.
So whether or not completed tasks are still visible in the GUI depends on the window extent, which you can change via the GUI workflow menu.
[UPDATE] see also this thread
2024-02-16T17:43:35Z WARNING - Partially satisfied prerequisites:
* 20240208T1200Z/scrub_ready is waiting on ['20240208T1200Z/publish_complete:succeeded']
* 20240208T1200Z/publish_ready is waiting on ['20240208T1200Z/postprocessing_task:succeeded']
Are you saying that the upstream outputs listed there, which are still being waited on, were actually completed?