- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2025 05:56 AM - edited ‎08-05-2025 12:00 AM
I've been given a task to deal with a lot of error logs being generated. I need to locate these errors and stop them from being logged.
The logs are coming from "com.glide.ui.ServletErrorListener" and the message says "Requested URI does not represent any resource: /now/uxframework/user_override/shortcut: no thrown error."
How can I find where this issue is happening?
ref:
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
After extensive debugging, I discovered that the issue is caused by an API call named "shortcut" from the file "uxasset/externals/ais-sn-components/index.jsdbx?sysparm_use_cache_buster=true&uxpcb=xxxxxxxxxxxxx." This problem occurs whenever a user opens a UI page. You can verify this by right-clicking on the browser page, selecting "Inspect," and navigating to the "Console" tab. There, you'll see an error message: "https://<company url>/api/now/uxframework/user_override/shortcut 400 (Bad Request)." Additionally, in the "Network" tab, there is a service called "shortcut" that shows a red 400 status code. This issue is related to code provided by ServiceNow, and it has been resolved in Yokohama Patch 5. If the instance is upgraded to Yokohama Patch 5 or later, the problem will be fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2025 02:50 AM
I have the same question! We are getting around 7k of these errors daily.
Requested URI does not represent any resource: /now/uxframework/user_override/shortcut: no thrown error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
After extensive debugging, I discovered that the issue is caused by an API call named "shortcut" from the file "uxasset/externals/ais-sn-components/index.jsdbx?sysparm_use_cache_buster=true&uxpcb=xxxxxxxxxxxxx." This problem occurs whenever a user opens a UI page. You can verify this by right-clicking on the browser page, selecting "Inspect," and navigating to the "Console" tab. There, you'll see an error message: "https://<company url>/api/now/uxframework/user_override/shortcut 400 (Bad Request)." Additionally, in the "Network" tab, there is a service called "shortcut" that shows a red 400 status code. This issue is related to code provided by ServiceNow, and it has been resolved in Yokohama Patch 5. If the instance is upgraded to Yokohama Patch 5 or later, the problem will be fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2025 02:56 AM - edited ‎08-07-2025 02:57 AM
@Girish Galla @RichardSaunders
Check the REST APIs configured and resolve the issue. Refer below link for troubleshooting,
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0863480
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
After extensive debugging, I discovered that the issue is caused by an API call named "shortcut" from the file "uxasset/externals/ais-sn-components/index.jsdbx?sysparm_use_cache_buster=true&uxpcb=xxxxxxxxxxxxx." This problem occurs whenever a user opens a UI page. You can verify this by right-clicking on the browser page, selecting "Inspect," and navigating to the "Console" tab. There, you'll see an error message: "https://<company url>/api/now/uxframework/user_override/shortcut 400 (Bad Request)." Additionally, in the "Network" tab, there is a service called "shortcut" that shows a red 400 status code. This issue is related to code provided by ServiceNow, and it has been resolved in Yokohama Patch 5. If the instance is upgraded to Yokohama Patch 5 or later, the problem will be fixed.