- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2024 03:16 AM - edited 08-22-2024 06:31 AM
@Daniela @Nikita @Caelan @Darius @janet
Hi,
I've made the changes to the service operation workspace using related script include from sys_ux_client_script_include and added two widgets in that SOW overview.
The widgets were successfully added in the SOW overview and shows the data as well.
But once clone has been done from prod to dev instance the service operation workspace shows error in dev instance.
Error was like:
Exception while executing request: null. Exception while executing request: null Check logs for error trace or enable glide.rest.debug property to verify REST request processing. Contact your ServiceNow administrator for more information.
I've added the screenshot below.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2024 03:40 AM
@Bhavya11 Are you sure this error will be resolved by upgrading to the most recent version?
if possible could you please share the snaps of this PRB1764833 article?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2024 04:23 AM
what you did for it? Could you please elaborate more your answer so that I can try it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 01:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2024 10:20 PM
The errors were resolved by glide.analytics.cache.enabled system property.
We just need to set the sys_property value to false.
That's set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2024 03:23 AM
Hi @AishwaryaS1 ,
It turns out this is related to a recently created PRB (PRB1764833).
The problem ticket is to be investigated further by Service Now's dev team, but it looks like this issue has been resolved in the latest version of Washington.
Upgrading to the most recent version, 25.3.1, resolved these errors in our instance.
Please mark helpful & correct answer if it's really worthy for you.
Thanks,
BK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2024 03:40 AM
@Bhavya11 Are you sure this error will be resolved by upgrading to the most recent version?
if possible could you please share the snaps of this PRB1764833 article?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2024 04:15 AM
yes, in our case it resolved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2024 04:23 AM
what you did for it? Could you please elaborate more your answer so that I can try it?