Inbound Email Action vs Inbound Email Flow Performace

[GrazielleB]

I am looking to replace our inbound email actions with Inbound email Flows. We have about 30+ currently running against every inbound email that I am hoping to replace and was wondering if anyone has made this move. If so, have you run into any issues with performance or anything else?

Thank you in advance

[JenniferRah]

I don't have an answer to your question, but I'm curious as to why you are switching to Flows?

[GrazielleB]

We are a service provider, and we create inbound actions for some of our customers to fulfill their case routing needs. The issue we are facing with inbound actions is that all of them run against every single email that comes in. Right now, we are not seeing any performance issue but want to get ahead of the game as we will continue to grow and add more rules. 

[JenniferRah]

Are you utilizing the "Stop Processing" checkbox in your inbound actions? That should reduce the number that are processed as once it hits the right one, it will stop.

We haven't had any issues with performance with inbound actions, but we haven't tried to use Flows for it, so I don't have anything to compare it to.

[Mark Manders]

Not with performance, but we did this with email actions that were calling script includes to check on certain things to either create/update a record, or lookup data.

When you start with this, be sure you know all exceptions and also all of the script includes that are being used. 

Be aware that inbound flows run first and actions after that, so you can run them next to each other, as long as you realize this.

Also: if not yet on your instance, create the system property 'glide.hub.flow.inbound_email_trigger.show_advanced' and set it to true. It will give you some extra fields on the trigger condition (like 'stop processing') that aren't there OOB.