Flows stuck in queued state even though the trigger conditions are met

[tadabala]

In our environment, the flows are getting stuck in a queued state even though the trigger conditions are met.

I've observed that:

• The flow name appears as empty in the sys_flow_context table for both Incident and Request tables.

• However, flows for SLAs are executing correctly.

• The flow.fire event is also stuck in a state showing a garbage value.

Tried the process from the below thread but it did not workout for my issue.
Link: https://www.servicenow.com/community/developer-forum/all-flows-in-queued-state-in-flow-engine-contex...

Has anyone else encountered this issue or found a workaround?

[kaushal_snow]

@tadabala ,

It sounds like your flows are stuck in queued because the underlying flow.fire events aren’t being processed (and sys_flow_context ends up with blank flow names) so you should check whether the Flow Engine Event Handler job in sys_trigger is stuck or disabled and verify for a backlog in sysevent, because if that job isn’t running properly the flow contexts never get picked up to execute.......

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[Bhuvan]

@tadabala 

Follow below articles for troubleshooting & resolution

https://noderegister.service-now.com/kb?id=kb_article_view&sysparm_article=KB1179826

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2271950

If this helped to answer your query, please mark it helpful & accept the solution. 

Thanks,

Bhuvan