Inbound action not triggering
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2022 07:01 AM
Hi,
I had a requirement when a email sent to abc@companyname.com email address it should receive from servicenow. and should create a record in exception table.
the email already configured before for the instance is xyz@companyname.com.
So how system admin configured this was, whatever the emails received for abc@companyname.com will route to xyz@companyname.com.
So, after this configuration my inbound action is not triggering.
emails are recieved to servicenow. But it is not creating any record. even I put logs in the inbound action cannot see them printing in the system logs.
Please help someone to sort this issue! what can be the reason for this
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2025 01:51 PM
I am also having this issue. I get the following syslog_email records in the Email Log related list on the Email record: "Email is classified as reply for triggers execution", "Ready for update", as well as one log showing the "Received id=", but no logs about inbound actions. They aren't being skipped, it's like they aren't being processed at all. I can trigger them by clicking the "Reprocess Email" UI Action.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2025 08:15 AM
Hi,
I am also facing the same issue. Did anyone found any solution for this. @Ankur Bawiskar can you please help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2025 08:29 AM
Please post a new question as this is an old thread.
share all the details along with screenshots.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2025 03:25 PM
So I did some trial and error and it worked for me. The Execution order of my Inbound Email Action was 100 and some of the working inbound actions in my instance either does not have a Execution order or Execution Order is 0. So I also removed the Execution Order from 100 to blank. And it created an incident.
Just wanted to let all know. Maybe someone else struggling with this and Execution order fixes the issue 🙂