Inbound Email Flow Not Triggering - Different Flow Executing Instead

Go to solution
vishokmohan
Tera Expert

3 weeks ago

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?

0 Helpfuls
  • 617 Views
2 ACCEPTED SOLUTIONS

Go to solution
Zach Koch
Giga Sage
In response to vishokmohan

3 weeks ago

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

If this information helped resolve your issue, please remember to mark response correct and thumbs up to help future community members on this information, thanks!

View solution in original post

Go to solution
vishokmohan
Tera Expert
In response to Zach Koch

3 weeks ago

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.

View solution in original post

0 Helpfuls
5 REPLIES 5

Go to solution
vishokmohan
Tera Expert

3 weeks ago

In few cases even when the system property glide.hub.flow.inbound_email_trigger.show_advanced is activated, flows created before enabling this property fail to display the advanced inbound email trigger fields Order and Stop processing .

 

Problem Details

Administrators activated the system property glide.hub.flow.inbound_email_trigger.show_advanced to expose additional configuration options for inbound email triggers. Despite the property being set to true, flows that existed prior to this change do not show the Order and Stop processing fields in their inbound email trigger configuration.

 

Reproduction Steps

  1. Navigate to Flow Designer

  2. Open an existing flow with an Inbound Email trigger

  3. Expand the Inbound Email trigger section

  4. Verify that the Order and Stop processing fields are not displayed

Root Cause

The system property glide.hub.flow.inbound_email_trigger.show_advanced only takes effect when a trigger is initially created. Flows constructed before the property was enabled retain their original configuration schema and do not automatically inherit the advanced field visibility.

 

Solution

The inbound email trigger must be reelected to force Flow Designer to apply the current property settings and render the advanced fields.

 

Resolution Steps

  1. Open the affected flow in Flow Designer

  2. Expand the Inbound Email trigger configuration

  3. Click the Trigger dropdown menu and reselect Inbound Email from the list

  4. Verify that the Order and Stop processing fields now appear

  5. Click Done to confirm the trigger configuration

  6. Save and reactivate the flow

Reference Article: Advanced inbound email trigger fields not visible after enabling system property 

0 Helpfuls