I can't say I have ever encountered this before.

Out of curiosity you could review this thread:

https://community.servicenow.com/community?id=community_article&sys_id=36a73b95db6edcd49e691ea6689619d1

It has suggestions around testing Wait for a duration of time actions in flows. More so, it details where to look up the event record for that activity. You could review that event record - does it have the correct 'Process On' date/time you expect. Does it appear if the record has actually processed but the flow was not updated to reflect that?

You might stumble on something that helps..

Alternatively; can you test the same flow on an alternative instance (one that isn't your personal development instance) - do you get the same result?

Geoff

Sumit Maniktala
Kilo Expert

There seems to be no reason for this not to run other than that the job responsible for this flow is awaiting in background for its time slice. Can you try changing the  "Where to run the flow" setting to "Run flow in foreground" under Advanced Options in Trigger and see if that works?

This is just to see if the issue is in flow or processing, we have to revert back as running in foreground will block user session 


Also can you expand that line 7 & share the screen shot?

 

Hope this helps 

Hi Sumit. I tried changing it to "Run flow in foreground" but its still in waiting state. 

I tried with 10 seconds and it worked. But then I tried with 2 min and it didn't worked. It went back to waiting state. Seems like only 10s is working fine

And here is the screen shot for line 7. I tried it with 2min

find_real_file.png

 

find_real_file.png

 

Simran7
Tera Contributor

Here is the screen shot for line 7

I tested for 2 min on my PDI and it works. The only thing worth noticing is that though flow performs the required action after the timer duration is over but this view of flow execution doesn't refresh on its own.  You have to press that refresh icon on top (before that waiting status) to see the step where flow has reached after timer is elapsed. Are you saying even after refresh the view is stuck here?