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.
Look Up Records action intermittently fails if pill representing a Reference is used in the condition and a previous Update Record action was executed on the source record of the pill. - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Look Up Records action intermittently fails if pill representing a Reference is used in the condition and a previous Update Record action was executed on the source record of the pill.
KB0861934

Look Up Records action intermittently fails if pill representing a Reference is used in the condition and a previous Update Record action was executed on the source record of the pill.


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

Description

A service catalog flow that updates the sc_req_item and then looks up records with a condition that uses a pill representing a reference may result in the look up records failing to find any records due to the name of the table being used in the condition rather than the sys_id of the reference.
The failure occurs intermittently without making any alterations to the flow.

Steps to Reproduce

1. Import attached update set.
2. Order "Apple Ipad 3" several times.
3. Inspect flow contexts in FD Ops View.
4. Observe that some executions succeed finding 1 record with condition "u_catalog_item=060f3afa3731300054b6a3549dbe5d3e" using sys_id and that some other executions fail and find 0 records and the condition differs "u_catalog_item=pc_hardware_cat_item" using table name where sys_id was expected.

Workaround

Modify the conditions to explicitly specify Sys ID i.e "Trigger->Requested Item Record->Item->Sys ID" rather than "Trigger->Requested Item Record->Item".


Related Problem: PRB1439445

Potentially Seen In

There is no data to report.

Fixed In

Paris Patch 4
Quebec
Rome

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.