Inbound Email Flow Not Triggering - Different Flow Executing Instead

[vishokmohan]

I have configured an inbound email flow in my custom application with specific trigger conditions. However, when an email is received, my intended inbound email flow is not triggering. Instead, a different flow is executing.

Current Behavior:

• Expected inbound email flow does not trigger

• A different flow executes instead when emails are received

• Trigger conditions are configured

What I've Checked:

• Email conditions appear to match the incoming email criteria

• Flow is active and published

• Trigger conditions are properly defined

Questions:

1. How can I control the execution order of multiple inbound email flows to ensure my specific flow executes first?

2. Is there a way to prevent other flows from processing the same email once my flow executes?

3. Are there any hidden settings or properties that might affect which flow triggers?

[Zach Koch · Accepted solution]

Just create the property with the values shown in the picture.

[Zach Koch]

Take a look at this article. You can add the Execution order to the flow so that you can set its priority higher than the other flow that is running. In ServiceNow, on an Inbound email, it will look through Inbound Actions and Flows, and when it finds one where it meets the condition, it will run that one (based on the Execution order) and then do a "Stop Processing" order and will no longer look for any Inbound Actions or Flows to run. 
Article how to add Execution order to your flow 

[vishokmohan]

@Zach Koch , 

I reviewed the article and attempted to check the "glide.hub.flow.inbound_email_trigger.show_advanced" system property, but I was unable to locate it. Has this property been deprecated, or is there an alternative way to achieve the same functionality?

[Zach Koch · Accepted solution]

Just create the property with the values shown in the picture.

[vishokmohan · Accepted solution]

From my understanding, it will not function properly if created in any scope other than Global. If I add the system property within the custom application, it may not behave as intended. On the other hand, if I create it in the Global application, I won’t be able to include it as part of my custom application files, which is required since the application will be published in the Store. This needs to be handled carefully.

To overcome this, I will create the system property in the Global scope and define it as a prerequisite for my application. The property glide.hub.flow.inbound_email_trigger.show_advanced will be of type true | false, set to true, and I will update the order and stop processing settings accordingly. This approach will work.