Workspace console warning "Invalid attribute value set for key: updatePayload"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hello,
We have developed a custom workspace in our instance and are encountering a large number of console warnings in the browser developer tools.
The warning message is:
Invalid attribute value set for key: updatePayload
These warnings appear to originate from an out-of-the-box ServiceNow script (trace points to @ui-core-bundle.jsdbx).
Key observations:
The warning appears on any workspace page.
It reoccurs on every action taken inside the workspace — navigation, button clicks, etc.
The warnings repeat frequently and can quickly fill the console.
The source seems to be tied to internal workspace rendering events (SEISMIC_COMPONENT_RENDER_REQUESTED).
Screenshot for reference is attached.
Has anyone experienced similar warnings in a workspace environment?
Do you know the cause or origin of this warning, and whether it is expected behavior or something that requires configuration changes?
Any insights would be appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
I have read about this earlier, but I can't seem to find the post. I do know that it was mainly console garbage and didn't impact the functionality of the workspace. Is anything not working with your app?
It feels like you are passing an updatePayload value that doesn't match with what is expected. Do you have a custom component or client controller that sends 'updatePayload' in an event? Check if the value matches the expected schema.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Try turning off the Next Experience Developer Tools browser extension and opening a new page.
The message appears to be being filtered up in the process of that extension tracking the events being emitted by the components on the page. When I'm not tracing something, I've found just leaving that extension turned off gets rid of a lot of the console noise.