Flow designer is stuck in waiting state after using "Wait for a duration of time" flow logic

[Simran7]

Hi, I am new to Flow designer. I am trying to send reminder notifications after 3 business days and just for testing purpose I am sending notifications after 10 min. For this I am using "Wait for a duration of time". 

The issue is Its always stuck in waiting state even after 10 minutes has been passed

Here is the screen short of my flow designer "Wait for a duration of Time" step

And here is the output after running my flow designer and it always stuck on waiting state

Please help me with this. Any advice will be appreciable. 

[TJ29]

I've just started getting this in DEV after a clone from production. Happens on either 'Wait for a duration of time' or an AD action. Anyone had any luck sorting it?

[Michal Fish]

Hi,

the same here ... PROD to DEV clone has been done recently and the behavior is the same, like described above.

Timer more than 10 seconds stucks.

Did anyone already raised it to HI Support?

[TJ29]

Hi Michal, 

Spoke with HI and they provided this KB article and some advice.

1. Export to XML all Flow Engine Event Handlers as back up '/sys_trigger_list.do?sysparm_query=nameSTARTSWITHFlow%20Engine&sysparm_view='

2. Create property com.glide.hub.flow_engine.event_handler.workers to 0 (this will delete all FEEH)
Delete any remaining FEEH jobs so that we can start fresh (if any)

3. Set com.glide.hub.flow_engine.event_handler.workers to 4 (for example) (this will recreate them)

Check that the jobs are created then delete the property. This should fix the issue with slow timers being processed, but try only in SUB-PROD.

Hope this helps

Taylor

[Ryan Harrington]

TJ,

Did HI give any indication of a permanent fix coming in a future patch / release?

[TJ29]

Hi Ryan, 

Turns out post clone the Flow Engine Event Handlers had empty sysids. Their response 'This issue could be is related with Instance Clone is not clearing records from sys_properties and sys_trigger table as described in PRB1415852.
Deleting FEEH that has empty sys_id should be part of cleaning upon cloning to avoid this issue.' I can't locate the PRB though.

Wonder if a exclude/preserve could be made use of here but it's not a big fix anyway, once you know it. Hope this helps.