- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2025 11:54 AM
I found a couple articles that sound like what we are now experiencing after upgrading to Yokohama and it sounds like this has been a bug since around Orlando visual-task-board-cards-not-auto-refreshing. It used to be that when we made changes to tasks, they would update on our visual task board within seconds. Now, we have to click the refresh button to get everything refreshed. Does anyone know when/if it will be fixed?
Thank you, Charles
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2025 11:56 AM
You're correct — this is a known issue that has existed since earlier releases, including Orlando, and it appears to persist or resurface in Yokohama. The problem is that Visual Task Boards (VTBs) no longer auto-refresh in real time when task records are updated elsewhere. This is particularly noticeable in collaborative environments where multiple users work on the same board.
What’s happening
Previously, VTBs had a real-time sync mechanism using GlideSocket (real-time messaging) or a similar channel, which would automatically reflect changes (like status updates, reassignments, or comments). In newer releases, this auto-refresh behavior may have been:
Broken due to platform changes
Disabled due to performance concerns
Affected by updated client scripts or changes in the WebSocket connection handling
Current workaround
There is no confirmed permanent fix from ServiceNow yet (as of Yokohama). Workarounds include:
Manual refresh using the top-right refresh button on the board.
Use of browser-based auto-refresh extensions (not recommended in production).
Custom client-side polling logic (possible, but not ideal or officially supported).
Next steps
Check Known Error or Problem Records
Search HI or Known Error articles (like KB0868306 or similar) related to Visual Task Board behavior for your version.
Open a Support Case with ServiceNow
Reference prior bug IDs like:
PRB1407781 (for earlier releases)
PRB1451397 (real-time updates and socket issues)
Monitor Release Notes and Patch Fixes
Review the Yokohama patch notes for updates related to VTB or GlideSocket.
Recommendation
If this functionality is critical to your team's workflow, and real-time updates are expected, consider filing a support ticket with ServiceNow Support. Include browser logs and reproduction steps, and reference that this worked in previous releases. They may be able to escalate the issue or offer a targeted fix depending on your instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2025 11:56 AM
You're correct — this is a known issue that has existed since earlier releases, including Orlando, and it appears to persist or resurface in Yokohama. The problem is that Visual Task Boards (VTBs) no longer auto-refresh in real time when task records are updated elsewhere. This is particularly noticeable in collaborative environments where multiple users work on the same board.
What’s happening
Previously, VTBs had a real-time sync mechanism using GlideSocket (real-time messaging) or a similar channel, which would automatically reflect changes (like status updates, reassignments, or comments). In newer releases, this auto-refresh behavior may have been:
Broken due to platform changes
Disabled due to performance concerns
Affected by updated client scripts or changes in the WebSocket connection handling
Current workaround
There is no confirmed permanent fix from ServiceNow yet (as of Yokohama). Workarounds include:
Manual refresh using the top-right refresh button on the board.
Use of browser-based auto-refresh extensions (not recommended in production).
Custom client-side polling logic (possible, but not ideal or officially supported).
Next steps
Check Known Error or Problem Records
Search HI or Known Error articles (like KB0868306 or similar) related to Visual Task Board behavior for your version.
Open a Support Case with ServiceNow
Reference prior bug IDs like:
PRB1407781 (for earlier releases)
PRB1451397 (real-time updates and socket issues)
Monitor Release Notes and Patch Fixes
Review the Yokohama patch notes for updates related to VTB or GlideSocket.
Recommendation
If this functionality is critical to your team's workflow, and real-time updates are expected, consider filing a support ticket with ServiceNow Support. Include browser logs and reproduction steps, and reference that this worked in previous releases. They may be able to escalate the issue or offer a targeted fix depending on your instance.
