Duplicate info messages on Workspace form (Business rule)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 12:40 AM
Hi,
I have a business rule running on insert of change request and creating a publication record. The issue is it's showing the info message and error message two times in the workspace however it is working fine in native UI. Please let me know if you have the solution for it.
FYI: It's not only related to this particular business rule, all the messages are showing duplicate in workspace.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 03:58 AM
Hi @Vaibhav K Yadav,
can you double check there are not two business rules triggered at similar time?
You could be able locating the BRs by the text from the messages, then you will see if there are two.
And if just one, then review its content.
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 04:14 AM
from your screenshot both are info message and none is error message
did you check any OOTB business rules which have info or error message?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 05:43 AM
Hi @Ankur Bawiskar , @GlideFather
The issue is not related to any specific business rule. All kinds of info messages and error messages are showing two times in the workspace.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 05:51 AM
@Vaibhav K Yadav do you have SNUtils extension installed to your browser?
if so, you can use a slashcommand "/code" and try to search for configurations that cause this, it might be a client script. Exmplae of use "/code your error message" + enter.
Based on that you should be able locate what script/configuration is responsible for that..
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */