PDI dev409776 Offline with 502 Bad Gateway — please preserve data
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
My Personal Developer Instance (PDI) dev409776 shows Offline in Manage My Instance. I clicked Refresh, but it remains Offline. Opening the instance returns 502 Bad Gateway.
Could you please check whether this is an infrastructure or maintenance issue and help restore access while preserving my instance and its data? Please do not release, reset, or wipe it.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi @jassimultan ,
There is no dedicated support available for PDIs.
Recently so many issues have been reported with PDIs. Instances are being reclaimed even when actively in use and some are unexpectedly transitioning to an Offline state.
To avoid losing any important data or implementations, make sure to take regular backups of your work.
If your PDI becomes unavailable, wait for 1–3 days, as it may become Available again during this period.
Thanks
Anand
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi @jassimultan ,
Don't panic! A 502 Bad Gateway error generally indicates a server-side or connectivity issue. It does not necessarily mean that your PDI or its data has been permanently lost.
You can refer to these community discussions where other developers have reported similar PDI offline and 502 Bad Gateway issues:
My suggestion:
Wait for some time and periodically check your instance status in Manage My Instance.
Avoid releasing or resetting your instance if you want to preserve your existing data.
Once the instance is accessible again, take a backup of your important configurations and update sets.
Hopefully, this is a temporary infrastructure issue, and your instance will become available again. However, recovery cannot be guaranteed until ServiceNow confirms the instance status.
Hope this helps! If this resolves your issue, please mark the response as helpful and accept it as the solution.
All the best!
Regards,
Sandesh Powar
ServiceNow Rising Star
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi @jassimultan ,
I ran into the same 502 Bad Gateway error on my Australia-release PDI around the time the release patch was being applied. In my case the instance came back on its own after some time, and I didn’t lose any data.
Recovery time varies, though. Community members report anywhere from a few hours to a few days. Here is what I’d suggest:
- Don’t release or reset the instance. Releasing permanently deletes all data. As long as the instance still appears under Manage My Instance, you still own it.
- Be patient with Refresh. Click it once, then wait and check back every few hours instead of refreshing repeatedly, since some users report that repeated refreshes prolong the outage.
- Wait up to a few days before considering a new instance. If it stays offline well beyond that, post your instance name, release, and the error in the Developer Community forum, since PDIs have no official support.
Once it’s back, I’d also recommend exporting your work (update sets ), because PDIs have no backup guarantee.
Related threads on the same issue:
- 502 Bad Gateway (snow_adc) PDI Offline
- Personal Developer Instance dev382137 is Offline (502 Bad Gateway)
- PDI got 502 Bad Gateway while developing, instance now offline
- PDI dev295777 Offline - 502 Bad Gateway
Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @jassimultan,
This is an offical answer from ServiceNow, you can refer for your current situation as well.
If you find my answer useful, please mark it as Helpful and Correct. 😊
Regards,
Soham Tipnis
ServiceNow Developer || Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10
