Have seen some reports of the final message being out of sync potentially. Where the completion message is sent before the last running message so the status gets reset to running but retains all the conditions of being complete
Could also be an issue in core with processing messages, but I haven't been able to spot in the logs in time. Need to see if it is possible to replicate locally
Have seen some reports of the final message being out of sync potentially. Where the completion message is sent before the last running message so the status gets reset to running but retains all the conditions of being complete