It shouldn’t require the user to fire an Execute Script just to store the record ID the workflow is being run on. This is pretty basic information and should be included with every Run. It’s difficult to know what record is affected, particularly if the workflow hasn’t even begun to fire yet. For instance, I just found a workflow “In Progress” since 6/13 but I don’t know what record it’s affecting.
Also there should be a button to kill an individual run, otherwise, what could the user do in this situation?
1 Like
I agree this would be very helpful for troubleshooting.
I have also run into that issue with “In Progress” flows hanging forever. I’ve found that in these cases the flow actually did execute, but somehow the log entry gets stuck. I usually do “Cancel all runs” on the flow, and as long as there aren’t any Scheduled or In Progress runs for that flow then that will take care of it without affecting anything else.
2 Likes