Apex Code Development You need to sign in to do that
Don't have an account?
SF ABC Flow wait element (interview) is not resumed as expected
Hi,
There is a wait element in my flow. One event (Wait_0_Minute) in the wait element is defined to run on "Absolute Time", which is set as "{!$Flow.CurrentDateTime}". The purpose of the wait element is to split big transactions to smaller ones to avoid hitting governor limits. The flow works well in Sandbox as expected so we deployed it in the production. Generally, it also works well in production but yesterday noticed there was a pending interview in "Paused and Waiting Interviews". Usually, the interview should be removed in a minute as soon as it is resumed as the event is supposed to run at "{!$Flow.CurrentDateTime}". But the Paused Date shows the interview has been paused for 6-7 hours. Today, the same thing happened.
The following is observed:
- September 19, 2017
Paused Date: 9/19/2017 6:54 AM
Disappeared (resumed): Around 9/19/2017 1:00 PM~2:00 PM
- September 20, 2017
Paused Date: 9/20/2017 6:51 AM
Disappeared (resumed): Around 9/20/2017 1:00 PM~2:00 PM
At present, we don't have other flows creating interviews and only have a few time-based workflow actions. So it is unlikely to hit the limits of time-based triggers (1,000 per hour, 24,000 per day, 20,000 at a time).
Can anyone help explain why the delay happened?
Thanks!
There is a wait element in my flow. One event (Wait_0_Minute) in the wait element is defined to run on "Absolute Time", which is set as "{!$Flow.CurrentDateTime}". The purpose of the wait element is to split big transactions to smaller ones to avoid hitting governor limits. The flow works well in Sandbox as expected so we deployed it in the production. Generally, it also works well in production but yesterday noticed there was a pending interview in "Paused and Waiting Interviews". Usually, the interview should be removed in a minute as soon as it is resumed as the event is supposed to run at "{!$Flow.CurrentDateTime}". But the Paused Date shows the interview has been paused for 6-7 hours. Today, the same thing happened.
The following is observed:
- September 19, 2017
Paused Date: 9/19/2017 6:54 AM
Disappeared (resumed): Around 9/19/2017 1:00 PM~2:00 PM
- September 20, 2017
Paused Date: 9/20/2017 6:51 AM
Disappeared (resumed): Around 9/20/2017 1:00 PM~2:00 PM
At present, we don't have other flows creating interviews and only have a few time-based workflow actions. So it is unlikely to hit the limits of time-based triggers (1,000 per hour, 24,000 per day, 20,000 at a time).
Can anyone help explain why the delay happened?
Thanks!
- Go to Setup ->Monitor ->Time-Base Workflow, click on "Search", then a message says:
"Note: You have reached the maximum number (1,000) of deletable Workflow Queue at one time. If you would like to delete more Workflow Queue, first delete the ones below and then perform another mass delete."
Ie, there are 1000+ time-based triggers are fired and queued. The new flow interviews have to wait for more time than usual or may not be excecuted.
My original assumption that we have only a limited time-based workflow triggers is not correct.