Error Handling not triggering on subflow error

[Dazler]

Hi,

We have been getting the error on many of the OOB actions that run in the Mid server, Cancelled : error="Failed to update plan context: xxxxxxxxxxxxxxxx from MID".  While we are working with HI Support and our networking team to determine the cause, I have been assigned to create an error handling for this.  The issue that I am running in to is the Error Handling section is on, but when this error happens it does not trigger the error handling.  It just stop this subflow, but the main flow keeps moving.  As you can see I even tried using a try and catch but for some reason it is not working.

This error doesn't return anything back to the action, it just errors.

Any help would be appreciated.

[James Chun]

Hi @Dazler,

It's difficult to see where the issue is coming from in the screenshot.

Can you share some screenshots of the main Flow and the subflow's execution details?

Cheers

[Dazler]

Hi @James Chun 

The error never makes it to the main flow.  This is the subflow execution and the error happens at the Add User to Group action which is an OOB action.   For someone reason, this error does not propagate from the Mid Server to the action status as an error it just stops that subflow and then continues running the main flow.

[James Chun]

Hi @Dazler,

It appears that the issue is coming from the MID server's connection.

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

This is just a wild guess but it might be possible that the OOB action does not cater to this type of error and simply terminates the flow/subflow.

Since you have already tried using the try/catch and the error handling, I am not sure if there is a way to catch the error without customizing the OOB Action.

You could also ask the Support agent how to catch these errors.

[Dazler]

Hi @James Chun,

I think I may have found a work around for this. 

I created a separate subflow for that OOB action "Add User to Group".  Within that subflow, I assigned a subflow output to get the context ID of the subflow when it runs.

Since only the subflow stops and the parent flow continues.  In my parent flow, if the output from that subflow where I put the context ID is empty that means that it errored and I am able to create the error handling in the parent flow.

Here is an example of the subflow: