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.
After creating a record in connect, the agent is logged out and switched to the guest account. - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • After creating a record in connect, the agent is logged out and switched to the guest account.
KB0715721

After creating a record in connect, the agent is logged out and switched to the guest account.


441 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

After creating a record using a Connect action, such as Create Incident, the agent is logged out and switched to the guest account.

Steps to Reproduce

 

1. Remove end-user access to sys_user records using a before query Business Rule, so that the end user cannot impersonate back to the agent.
2. Initiate a connect support conversation between the agent and the end user.
3. As the agent, use the create incident connect action.
4. Fill out the mandatory fields and submit the record.

Observe the record is submitted, but you cannot send any more messages, and if you refresh you are logged in as the guest user. The backend code which causes the agent to impersonate the end user to check some permissions and then impersonate back to himself and if the end user of the conversation cannot see the sys_user record for the agent, he cannot impersonate back. When this happens we default to the guest account.

Workaround

This issue was fixed in Jakarta. The workaround on earlier releases was to disable or edit any Before Query Business Rule on the sys_user table, so that end users can see the agent records, and are able to impersonate back.


Related Problem: PRB1298699

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.