Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Unable to locate incident ___SYS_ID_NUMBER___ for inbound email processing due to different domains - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Unable to locate incident ___SYS_ID_NUMBER___ for inbound email processing due to different domains
KB0751477

Unable to locate incident ___SYS_ID_NUMBER___ for inbound email processing due to different domains


6359 Views Last updated : May 12, 2023 public Copy Permalink
KB Summary by Now Assist

Issue

Steps to reproduce

  • Check the sys_email record
  • Check any affected incident number INCXXXXXXX
  • You will find it was not updated properly, the sys_email record will show the next message:
  • Unable to locate incident ___SYS_ID_NUMBER___ for inbound email processing

Troubleshooting


  1. Go to the sys email record: /sys_email.do?xxxxxxx
  2. Identify the user field for that record
  3. Verify user has required roles to access incidents (itl, itil admin or admin)
    • If user has required roles continue below
    • If user does not have the required roles add them and retest or reprocess the email.
  4. Identify the target record from the email (incident number)
  5. Right-click on 'Show XML'. You will see the next information:
    If you go here, right-click the header, and select 'Show XML' you can see information similar to this
    <sys_domain>XXXXXXXXXXX</sys_domain>
    <sys_domain_path>!!!/!!!/!!&/</sys_domain_path>
  6. Compare both the user domain and the incident domain and they will be different

Cause

The incident belongs to a different domain than the user who sent the email

Resolution

If you consider the user AAAA in the wrong domain or want to know why it is different than expected and when it has changed - you can enable auditing on the sys_user table through the Dictionary entry here:

https://<instance-name>.service-now.com/sys_dictionary_list.do?xxxxx

Consider either changing the domain of the user, or the domain of the incident.

Note iconNote: This issue could occur after upgrading an instance or modifying the user records.


Note iconNote: Ensure these actions are tested in sub-production instances before implemented in production environments.

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.