PDI went Offline 502 error

[morwetshire]

I was working on my PDI it went Offline started writing the is a JavaScript error on my PDI I refreshed my site and it wrote 502 error 

502 Bad Gateway

---

snow_adc

[Dr Atul G- LNG · Accepted solution]

Hi @morwetshire 

If your ServiceNow Personal Developer Instance (PDI) has been stuck in the Refreshing state for more than 24 hours and is returning an HTTP 502 error, it is likely that the underlying infrastructure or node hosting your instance has encountered an issue.

Option 1 – Try Refreshing the Instance

1. Sign in to the ServiceNow Developer Portal.

2. Go to Manage My Instance.

3. Click the Refresh button (if available).

4. Wait for the refresh process to complete.

In some cases, the PDI may recover after a manual refresh.

Option 2 – Release the Instance and Request a New PDI

If your PDI continues to return an HTTP 502 error or remains stuck for more than 24–48 hours, I generally recommend releasing the instance and requesting a new Personal Developer Instance (PDI) from the Developer Portal.

Based on community experience, instances that remain in this state for an extended period rarely recover automatically.

Please note the following before releasing your instance:

• Provisioning times for new PDIs have increased significantly in recent weeks.

• Many community members have reported waiting 2–3 weeks or longer to receive a new instance, regardless of the selected release version.

• There have been multiple reports of PDI failures, provisioning delays, and general Developer Portal availability issues.

Unfortunately, no one can provide an exact timeline for when these issues will be resolved or when a new PDI will be provisioned.

For now, the best approach is to monitor your request status in the Developer Portal and be patient while waiting for your new instance to become available.

[Dr Atul G- LNG · Accepted solution]

Hi @morwetshire 

If your ServiceNow Personal Developer Instance (PDI) has been stuck in the Refreshing state for more than 24 hours and is returning an HTTP 502 error, it is likely that the underlying infrastructure or node hosting your instance has encountered an issue.

Option 1 – Try Refreshing the Instance

1. Sign in to the ServiceNow Developer Portal.

2. Go to Manage My Instance.

3. Click the Refresh button (if available).

4. Wait for the refresh process to complete.

In some cases, the PDI may recover after a manual refresh.

Option 2 – Release the Instance and Request a New PDI

If your PDI continues to return an HTTP 502 error or remains stuck for more than 24–48 hours, I generally recommend releasing the instance and requesting a new Personal Developer Instance (PDI) from the Developer Portal.

Based on community experience, instances that remain in this state for an extended period rarely recover automatically.

Please note the following before releasing your instance:

• Provisioning times for new PDIs have increased significantly in recent weeks.

• Many community members have reported waiting 2–3 weeks or longer to receive a new instance, regardless of the selected release version.

• There have been multiple reports of PDI failures, provisioning delays, and general Developer Portal availability issues.

Unfortunately, no one can provide an exact timeline for when these issues will be resolved or when a new PDI will be provisioned.

For now, the best approach is to monitor your request status in the Developer Portal and be patient while waiting for your new instance to become available.

[glideFather]

Ahoy @morwetshire,

to learn more details about PDI states, go to [GF#5] PDI in Offline state: Resolving Error 502 Bad Gateway (snow_adc)

[Tanushree Maiti · Accepted solution]

Hi @morwetshire 

Last week , I got 502 error in my PDI . After refreshing multiple times, It started to work after 2 hours. 

That time I did not login into Developer portal and Refresh.

For your case , if it is taking more time, keep refreshing it at certain interval. If possible from Developer portal.

Hopefully , it would be fixed.

Note: If after waiting 6-7 days, it does not work, then think about Release the instance and Request for new one.

[dellyou088]

Leave it for few hours, it will automatically will be UP for working

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards