Error : Inbound Action (Unable to locate the Record)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @Everyone,
Recently, we encountered an issue in the production environment, which has been live for about 4 months.
This issue is related to email-based HR case creation via inbound actions.
We observed that for some tickets, when an agent adds additional comments on the record or sends an email to the end user, most of the time, the user’s reply correctly links to the respective record. However, in a few cases, the response email is received and visible in the email logs, but the target record is not generated.
one such and error I'm posting below :
Can anyone please take a look and suggest what could be the possible cause of this issue?
Since this is in the production environment, what would be the safest way to test it?
For the records we tested, everything worked fine and we received the correct responses.
However, for some other records, we are seeing this kind of conflict.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @mdshahvez11 ,
Please Check you haven't checked Omit Watermark check box in the notification record. And check the "sys_watermark" table and see if the id in the error log has some records. If you find this answer helpful please accept the solution.
Regards,
Lithesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
No, Omit watermark is unchecked in notification.
I also checked the sys_watermark.list for the reference number of the received email that was not attached to its correct record , that is also present there with correct case number.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello, @mdshahvez11 .
The following knowledge might be helpful.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1301200
Thanks Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I came across a related topic.
