Creating a Flow (Flow designer) on the Flow Engine Context table doesn't work

[Sergio26]

Hello,

I'm trying to build Flow with Flow Designer on the Flow Engine Context table but the condition never triggers.

The goal of this is to create an incident when a certain Flow context results in an Error. Here is my condition (I tried only with the State criteria):

Anyone knows why is doesn't trigger. Is it because of the table?

Thank you

[Maik Skoddow]

Hi @Sergio 

I have no idea, why your Flow doesn't trigger but to be honest I would never have thought of handling a broken flow with a flow either.

Have you already thought about using a business rule?

And on Advanced tab you can enter the appropriate code for creating an Incident.

Kind regards
Maik

If my answer replied your question please mark appropriate response as correct so that the question will appear as resolved for other users who may have a similar question in the future.

[Sergio26]

Hello,

The Business rule was my second option but this means creating and maintaining code which I wanted to avoid. Also with Flow Designer I can easily create the incident and copy infos inside from the Flow context error.

I opened a case to ServiceNow to understand why the flow doesn't trigger. I think it might be the table (which is not available to report on). However if certain tables should not be allowed to be used with Flow they shouldn't be available to select.

Thank you

[Sergio26 · Accepted solution]

After ServiceNow reviewing my problem, turns out the Flow starts at state 'Waiting', then 'Queued', and then 'Error'. So the trigger should be an 'Updated' on the table and not a 'Created'.

It works as I wanted to and I can easily create an incident with some of the context infos including wich record was the Flow executed on.