Issue while creating Client script and Script Include
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi @BaijunathS,
maybe try to log out, clear cache and log in again to retry.
If not helped, then you can check the Access Analyser to understand the visibility constraints if there are any.
Other thing to do is to ask platform owner/lead admin to check it for you and last resort is to raise a case from the Support Portal.
100 % GlideFather experience and 0 % generative AI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Looks like an intermittent issue.
I agree with point mentioned by @GlideFather try to clear instance cache and logout and login again, that should help
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
“webpage is temporarily down or moved” message typically appears when a client script is trying to call a Script Include incorrectly, especially in cases where GlideAjax is not set up properly or the Script Include is not marked as Client Callable. Since it’s working for others, the problem is likely specific to your setup — for example, missing client callable = true, wrong Script Include name, or calling it directly instead of using GlideAjax.
