I have a wait node with a long-ish time interval (up to 10 minutes) that also happens to be random. This makes the live “execution display” really confusing. As you can see from the screenshot all I can tell from the UI is:
- It’s currently waiting
- The execution time before beginning to wait was 19ms
I don’t know:
- How long it’s been waiting for, or
- How much longer I have before the next step
Even if my delay weren’t random I’d want to be able to quickly tell when the delay will finish.
My proposal is to:
-
Update the “Waiting” on the left to the elapsed workflow time including the delay. As you can see, the “succeeded” time includes the delay, and I don’t think that knowing the time spent processing before the waiting started is helpful.
-
Add a countdown timer on the Delay Node. This countdown timer would show time remaining for both the resume=interval and resume=specified_time. It would be simple, like “04:32 remaining”. The highest resolution would be seconds (ie, no milliseconds), and lower resolutions would be added dynamically (e.g., “1:04:32 remaining”).
#1 seems straightforward. It does change the current behavior, but current behavior is inconsistent while waiting and I can’t think of a reason anybody would want to see the pre-waiting time?
#2 requires – as far as I know – a new UI element. A node-label during execution.