Inbound email action not creating any record in the custom table

[Karishma Dubey]

Hi,

I have created inbound email action and it is not working not creating any record. Condition is i will be receiving email from lets say xyz@test.com and subject = "test". I checked logs there is no error.

[Sudhir Urkude3]

Hi @Karishma Dubey ,

I noticed your inbound action isn’t being executed. The logs show:
"Stop processing detected by another Inbound action which is processed before your inbound action."

To resolve this, you have two options:

1. Adjust the condition of the existing inbound action so that it does not intercept your scenario.

2. Uncheck the “Stop processing” checkbox on that earlier inbound action.

**********************************************

If this helps, please mark the response as “Accept as Solution” and “Helpful” 

Thanks & regards,
Sudhir Urkude

[Karishma Dubey]

Yes it is running this inbound action. And the order of this inbound action is 1.hence no other inbound ations are running.

[Ankur Bawiskar]

@Karishma Dubey 

Is your inbound action getting skipped? It will get skipped if conditions don't match.

May be some other inbound action is getting processed and that inbound action has Stop processing checkbox as true and hence your inbound action is not getting triggered.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Mark Manders]

There is an error: your user is unknown. You have something custom taking care of that, but even if you would inactivate it, realize that the user emailing in needs to have the proper rights to create that record. Inbound email is handled through a sort of impersonation to validate if the user is allowed to create the record that the inbound action/flow is meant to create.
A solution would be to use an inbound flow and adding extra roles to the flow, so it always succeeds.

[GlideFather]

Hello @Karishma Dubey,

you are not sharing the upper part of the form:

Is the table selected properly, is it active? are not there several records with the same order?

Check also the canCreate() if it is in the Actions tab. 

Is it a production environment? the TEST or DEV can have this deactivated.

To find this out, navigate to :

...and you will see this: