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.
On flow designer, sub-flow is failing with error "Unable to load connection with alias ID: xxxxxxxxxxxxxxx" - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • On flow designer, sub-flow is failing with error "Unable to load connection with alias ID: xxxxxxxxxxxxxxx"
KB0832119

On flow designer, sub-flow is failing with error "Unable to load connection with alias ID: xxxxxxxxxxxxxxx"


4627 Views Last updated : Dec 12, 2024 public Copy Permalink
KB Summary by Now Assist

Description

In a sub-flow, if we set it to run-as user to the user who initiates a session and when the main flow was activated and triggered, the platform cached the flow and an error occurs. When the sub-flows "Run-As" "system" and saved, it doesn't take effect on the flow even though it shows the sub-flow was executed by "system user".

Steps to Reproduce

  1. Create a Subflow
    1. Run As - User who initiates session
    2. Actions – Log info message – “Subflow Test”
    3. Save and publish
  2. Create a Flow
    1. Run As – System User
    2. Trigger – new incident
    3. Actions –
      1. Log info message – “Flow Test”
      2. Add the Subflow from step #1
    4. Save and activate
  3. Create an incident to trigger the Flow
  4. Flow execution logs will show the Flow was executed by “System User” and the Subflow was executed by the user (Correct Result)


  1. System Logs will show the “Flow Test” message was created by “system” and “Subflow Test” was created by the user (Correct Result)


  1. Change the Subflow’s “Run As” property to “System User”, save and publish the Subflow
  2. Create an incident to trigger the Flow
  3. Flow execution logs will show the Flow was executed by “System User” and the Subflow was executed by “System User” (Correct Result)


  1. System Logs will show the “Flow Test” message was created by “system” and “Subflow Test” was created by the user (Incorrect Result)


Workaround

Making changes on the subflow and saving it it is not enough for the changes to apply. The correct process is to also publish the flow one more time after changes are made so they take effect on the following executions.


Related Problem: PRB1347366

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.