Flow engine context is in queued state and not executing

[srijamadhuri]

Hi,

Flow engine context for the flow is in queued state and not executed. 

If we go to flow designer and test - flow is triggered.

Is there any configuration where flow designer triggering to be enabled?

We used catalog item through record producer  - on create triggering the flow.

Attached the screenshot where you can see 2 flows are queued which came for service portal catalog form submission and other one which is in complete state from flow designer test .

 Anything over upgrade to verify?

[Atulit]

Hi, 

I am facing the same issue in Paris release. Has there been a solution for this issue.

[elle]

I'm facing the same issue in Quebec release, how did you fix it?

[Prasad Pagar]

Hi LP,

What you see in below?

Thank you
Prasad

[elle]

They are all in ready state, but not processed.

[Atulit]

Hi, 

One workaround for this is you can increase the timeout of the flow.

Usually, this happens if the flow is large and it takes a long time to load the flow in memory.

If you calling the flow/subflow from a scripted REST API then you can increase the time out as shown below.

var result = sn_fd.FlowAPI.getRunner().subflow('<subflow_name>').inForeground().withInputs(inputs).timeout(<time in ms>).run();

Also, another way is to use functions given by Flow API like ScriptableFlowRunner - quick() which runs the flow quickly without creating execution details or other related records.

More details related to Flow API could be found here: https://docs.servicenow.com/bundle/quebec-application-development/page/app-store/dev_portal/API_refe...