Tim Pillinger

Workflow so far... ```ini [scheduling] initial cycle point = 1919 [[graph]] R1 = foo & bar [runtime] [[foo]] script = """ cylc message -- "CRITICAL: Hello World" sleep 500 #...

So I can work out how to avoid logging duplicate polling messages (Check the new polled message against the activity log). But it's less clear at the moment how to...

Additional questions from a conversation with @dpmatthews : > Why does the job activity log appear to show two separate log events for each poll? It doesn't - it shows...

@metronnie - I think that I fixed it.

The original approach (adding messages to the activity log file and checking for them later seemed to break some of the workflow restart tests in ways that make me un-confident...

@oliver-sanders - I've left this in a draft state - could I have your thoughts on the issue around restart?

> > @oliver-sanders - I've left this in a draft state - could I have your thoughts on the issue around restart? > > I don't see what the issue...

> Last thing is that the `started (polled)` still piles up in the UI if you poll repeatedly  Rah!

> Actually I've just tested this with the UI and unfortunately no messages come through while the workflow is running, but when you stop it, duplicate messages can come through...

@MetRonnie > As it currently is. With all the changes since we started this convo?