Hilary James Oliver

> 1. If you stop a workflow can you restart it using play. This isn't true if you "stop" a flow. > 2. If you want to stop a flow...

`cylc play` has a similar dual purpose: to start a scheduler and to un-pause a running one.

Another thing that perhaps argues against using `cylc remove` to stop flows, unless we can interpret it as "removing flow numbers": If I want to stop flow 2, say, I...

Yes, I need to (re)-investigate that - I ~think I did it deliberately, and it seems to work correctly, but have forgotten my own chain of thought already... [DONE] A...

Sorry, poorly explained by me! - that was just intended to show that my changes to the task status DB calls had not broken anything.

~~(TBD: resolve Oliver's question above.)~~ DONE

Oops, sorry :face_with_spiral_eyes: should have thought of that myself!

(I'll take another look at this again soon - I'm keen to use it)

> How best to get around this? Is it safe to stick a try/except around this logic and expect the task_pool/task_proxy to rebuild it for us? Hmm, I think not...

Wait on fixing the DB json key hack from SoD. (@oliver-sanders might need to help me with this).