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.
When initiating a chat conversation the first message sent by the End User to the queue is missing also, after closing a chat session all messages disappear - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • When initiating a chat conversation the first message sent by the End User to the queue is missing also, after closing a chat session all messages disappear
KB0647536

When initiating a chat conversation the first message sent by the End User to the queue is missing also, after closing a chat session all messages disappear


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

Issue

Symptoms


  • Within Connect Chat, the initial message from the caller user does not reach the agent user, however subsequent messages go through successfully. When an end user initiates a conversation, the responding agent user accepts the chat, but does not receive the first message. 
  • Usually the chat window header will reflect the initial message of end user, hence customer could work-around the issue via using the chat window header for referring the initial message. However, when the message is longer than 160 characters, the chat window will truncate the text starting at the 161st character. This is due to the Short Description field being set OOB to 160 characters length. Trying to increase the Short Description length is not an allowed option, so users can not rely on the chat window short description for longer texts.
  • Also once the chat is end by end chat UI action by the agent or the user then on the refresh of the page the chat conversation is lost. The conversation is lost on both the sides of the agent and the customer and it wont be visible anymore.

Release


Kingston, Jakarta, Istanbul 

Cause


The Live Feed permission logic is set on the Comments field type on the main Task table. OOB, this is of type 'Journal Input'. If the Comments field type is set to anything different from 'Journal Input', the Live Feed permissions fail and cause the initial message from the user to not to reach the agent.

Resolution


Do not alter the field type of [task].[comments] or revert it back to the out of the box definition as 'Journal Input'. 

 


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.