Unable to locate incident (incident 'sys_id') for inbound email processing

Luigi Scungio
Tera Contributor

Dear all,

i have a problem to update incident by inbound email action.

When a not-user reply to a system mail, the inbound email processing return the error Unable to locate incident (incident 'sys_id') for inbound email processing.

The original email has the watermark and if the same thing is done by a user present in sys_user the incident is updated correctly.

Can you help me please?

find_real_file.png

1 ACCEPTED SOLUTION

SanjivMeher
Kilo Patron
Kilo Patron

What do you see in the email logs, which is at the bottom of email received? Did it make use of Update Incident inbound action. If yes, then you should add few gs.info to check, where it is failing


Please mark this response as correct or helpful if it assisted you with your question.

View solution in original post

7 REPLIES 7

Andrew Bettcher
Kilo Sage

We get this. There is an out of the box rule that prevents an "unknown" user from updating a ticket. Lets say you email a customer distribution group but the customer has changed who is in that distribution list without telling you. If one of the users responds and doesn't have a user record in ServiceNow then the email will be rejected.

 

There is a setting you can change that will automatically create new user accounts when an email comes in from an unknown. That's OK unless, like us, you have multiple "probes" out there emailing in automated faults. We turned this on in our DEV instance and within a few days we had over 200 new accounts, all belonging to fault nodes.....

 

We still get the error but we have set up a feedback loop for errored emails so we catch them and then manually process them (e.g. validate the user and, if valid, add the account and then, reprocess the inbound email.

Community Alums
Not applicable

Hello!

 

Something that helped me find the root of this problem (I had it too) was this Hi Service Portal Article.

https://hi.service-now.com/kb_view.do?sysparm_article=KB0751477

But basically, the problem is due the user that is sending the reply to that incident is from a different domain and might not have the roles (ACLs as well) to see things from different domains.

 

Hope I could help you with this!

 

Best regards,

 

Pedro

Andrew Bettcher
Kilo Sage

This came up for us again recently even though we "solved" it via a process change. It turned out that someone had created a duplicate user record using the same email address but a different user ID (the validation is only on the ID). 

Like all cases involving duplicates, ServiceNow has no way of working out which one is correct and so, rather than cause an issue, it just skips the records. I don't know fully what happened but HI said that it was due to the duplication and so we removed it.

We were just about to recommend that one of our business units use this method to manage customers that act as the contact for multiple customers....Multiple records with different user IDs but the same email. Lucky.