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.
The state field did not update on the change request record, other odd behaviors - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • The state field did not update on the change request record, other odd behaviors
KB0819714

The state field did not update on the change request record, other odd behaviors


1515 Views Last updated : Jan 3, 2025 public Copy Permalink
KB Summary by Now Assist

Summary

ISSUE SUMMARY:

  • fields did not update on [change_request] record
  • state field did not update
  • workflow ran but parent record did not update
  • Operation against file '<table_name>' was aborted by Business Rule 'SNC - Run parent workflows'
  • If a task or approval record was updated and fired off the workflow on the parent record, if the WF update is aborted the WF context will advance forward without updating the parent record, this situation will cause the parent record to be at an odd state with the WF

MOST PROBABLE CAUSE:

  • custom bus.rule where setAbortAction is called
  • in OOB configuration, the change management state model did not allow the update to record


When reviewing node logs we might stumble across the following entry:

10:37:27.205    Info    Default-thread-14   92C15D161B272254FC82773BDC4BCBD9    txid=0b662e551ba7 Operation against file 'change_request' was aborted by Business Rule 'SNC - Run parent workflows^c5f012d91b270854cf82773bdc4bcb55'. Business Rule Stack:SNC - Run parent workflows,P1-P2


However, after further review, we note that business rule "SNC - Run parent workflows" is out-of-the-box and no setAbortAction method is being called

So we're left wondering how was the transaction aborted?

In a normal transaction where GlideRecord is updating a record and triggers a Business Rule with the setAbortAction method, this BR would show up in the node logs, however, in this node log entry is different because 'SNC - Run parent workflows' is out-of-the-box and has no abort method.

Usually how this BR is triggered is when an [sc_task] or [change_task] is closed, this BR triggers "after" the database operation, this BR wakes the WF up on the parent task record, moves the WF forward and then attempts commits this changes to the parent task, it is at this point some business rule is aborting the operation.

If we review the node log entry again, we see a comma after the name 'SNC - Run parent workflows' what follows next is the BR that aborted the transaction. In this case, a custom BR is named: P1-P2

This could cause unexpected behaviors on the parent task record since this type of operation is intended to be aborted. If this is the case, then all customization where abort should occur would need to be re-evaluated before the [sc_task] or [change_task] is committed to the database.


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.