- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2026 07:04 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2026 12:59 PM
Hi @NuthanaA
The issue where the agent is not responding or showing a "Connection failed" error is typically tied to session handling or input clarity. Please try the following steps:
Improve the Prompt Strategy: The "Connection failed: WebSocket connection error" often occurs when the prompt is too vague for the agent to initialize a plan. Instead of a generic request like "I want an application," provide specific details
Check for Updates: Ensure your instance and Now Assist plugins are up to date. Sometimes a version mismatch causes the agent to hang or fail to establish a stable connection.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
Same issue. You can be as detailed as you want, specify every table name, field value and name, ui page, no matter what I do I get the same error.
It is a Websocket connection error. If it was a "Your prompt is garbage" error it would still return a response saying as much, but it doesn't.
This is the perfect time for ServiceNow to have this functionality working given they just obliterated everyone's PDI's, but it just doesn't work.