Hilary James Oliver

Right, so as I understand it that's the expected result - hence my issue above suggesting it would be nice to apply "pre-initial" logic to individual sequences not just the...

> As a consequence, to make a parent-less clock-triggered task queue immediately you will have to trigger it twice if abstract but only once if in n=0 Actually, that's similar...

Explicit works fine: ```ini [[graph]] # count backwards R3/P1Y/2010 = b[-P1Y] => b # boostrap into the sequence R1/2007/P0Y = b ```

Well the lone "backward" one doesn't work: ``` ._. | | The Cylc Suite Engine [7.9.9] ._____._. ._| |_____. Copyright (C) 2008-2019 NIWA | .___| | | | | .___|...

> and without inventing new terminology (e.g "abstract task"!). I have used that terminology on and off, to distinguish a "concrete" task (which is represented by a task proxy object...

Neither does your full example - so I'm confused! ``` oliverh@NIWA-1022450:~/cylc-src/dog$ cylc run --no-detach dog ._. | | The Cylc Suite Engine [7.9.9] ._____._. ._| |_____. Copyright (C) 2008-2019 NIWA...

(Anyhow, I gotta bail, it's late here ... I'll check follow-up comments in the morning).

@oliver-sanders - I tend to agree that ideally "trigger" should mean "run now", end of story. But the fact is trigger does have this "layered" behaviour already - for queued...

Cylc 7 stall with unsatisfied pre-spawned tasks, vs Cylc 8 shutdown with nothing to do - is expected under the circumstances - but I presume by "it worked at Cylc...

> It's just difficult to know the best way to describe this without referring to spawning and n=0 and without inventing new terminology (e.g "abstract task"!) That's not really an...