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.
Incident.reassignment_count is not "0" on new incident received via email inbound action - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Incident.reassignment_count is not "0" on new incident received via email inbound action
KB0832117

Incident.reassignment_count is not "0" on new incident received via email inbound action


1127 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Description

The value incident.reassignment_count is not "0" on new incident received via an email inbound action.

Steps to Reproduce

1) Enable email sending and receiving under "email properties".

2) Find "create incident" under "Inbound Email Action".

3) Edit and add "Action", "Field Action".

4) Set "Assignment Group" to e.g "Database".

5) Send an email to <instancename>@service-now.com. Verify the reassignment count is 1 instead of the expected 0.

Workaround

This is expected behaviour. By design incident.reassignment_count is intended to be zero when assignment group is changed via script, but it is set to 1 when the assignment group is changed via field actions in an inbound action.


There is always the option use either Field actions or scripts to increase the value or change the count value.


Related Problem: PRB1327464

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.