Hi,
This simply means that once the email was received by your instance, it reviewed appropriate inbound actions it may qualify for, once it found the first one (in execution order) it executed it. Then, within that inbound action settings, it had the "stop processing" checkbox checked. That merely means...stop. It won't continue to evaluate if that email qualifies for other inbound actions after it hits an inbound action with stop processing checked.
Normally emails are only going to be used within 1 inbound action and stop processing is common to prevent other inbound actions from also running.
Example: I get an email to request a specific catalog item, it's inbound action execution order is 10....once the email is evaluated for that inbound action and qualifies to be the one that is needed, it orders the catalog item like it's supposed to. Then....it looks to see if stop processing is checked or not...if not checked...that same email moves for further evaluation (now executing other inbound actions with a higher order than 10, etc.). Well, the last inbound action that I have is sort of a "catch-all"...and its set to create an incident if NO OTHER inbound action catches that email along the way. If the stop processing box is not checked in that first inbound action that email was using...not only did that 1 email order a catalog item, but NOW...we have an incident too...is that right? No.
Are you sure this is an issue?
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
