We have a flow that is that is triggered by the state of on hold and the on hold reason of awaiting caller. As part of this comments are mandatory but are not part of the conditions of the flow. Recently I noticed that an incident that was older then 30 days was still on hold awaiting caller when flow would normally have closed the incident after 4 days. I found and was able to reproduce the issue as the two incidents that where the flow did not work had 1 thing in common. The tech who put in the comments did "@" user how was the caller. This for some reason caused the flow set with all wait for duration to run at the same time. Any idea and using "@" in the comments would cause this? Example screenshot below of what the flow looks like in this condition. It basically has all the wait for durations set to the time the incident was updated but that is in the past by the time the flow actually start so it does not run.
