PDI Availability Issue? "Alert level: warning. We're having trouble opening your instance due to an"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
PDI has been up and working just fine prior to early Eastern hours today. Instance is showing as offline and just getting a "Alert level: warning.
Really just trying to determine if I should wait it out or request a new instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
ahoy @MySNOWDevAcct,
this happens here and there. Requesting a new instance might cause data loss from the previous instance (if you haven't made your backups) and there might be waiting queue to get a new instance so take this option as the last resort...
Only thing you can do is to wait a bit more, also you can go to Dev portal and click the Refresh button if available: https://developer.servicenow.com/dev.do#!/manage-instance
Workaround: if you want to check something really quick, enrol to a course (e.g. ServiceNow fundamentals) and it comes with a lab instance for a very few days but could serve you for something quick.
✂-----Cutting-out-the---✦AI-noise✦---All-replies-written-and-vouched-for-by-GlideFather---
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @MySNOWDevAcct,
From an architectural and operations perspective, this outage is a perfect, low-risk reminder of why disaster recovery protocols are critical. PDIs are provisioned on the lowest-tier infrastructure available and carry absolutely zero Service Level Agreements (SLAs) for uptime.
When building in any environment—even a free sandbox—you must architect your workflows for ephemeral infrastructure:
Always link your PDI to a remote Source Control repository (like GitHub) via the native Studio integration.
Commit your code frequently at the end of every development session.
If your instance is fully backed up to Git, a stalled node is a complete non-issue. You can simply release the broken instance, request a fresh one, and pull your repository down in minutes. If you have not backed up your work externally, you are unfortunately at the mercy of the free infrastructure's recovery queue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @MySNOWDevAcct,
This is a very common scenario with Personal Developer Instances (PDIs). Because PDIs share underlying server resources, an "internal error" usually indicates that the specific physical node hosting your instance is experiencing a stalled background job, such as an automated backup, hibernation script, or platform patch.
Here is the best technical approach to handle this:
Wait at least 24 hours before taking destructive action. The ServiceNow infrastructure team runs automated scripts overnight to forcibly wake or reboot stalled PDI nodes.
Do not constantly refresh the page, as this can sometimes reset the wake-up queue timer in the background.
Be aware that if you choose the "Release Instance" action from the developer portal, you will permanently lose all uncommitted local update sets and data.
If you have important data on that instance, wait it out. It is very rarely a permanent failure!
