504 Gateway Timeout and PDI Offline in ServiceNow Developer Portal

shobana_n
Tera Contributor

Hi everyone,

I am facing an issue with my ServiceNow Personal Developer Instance (PDI).

Issue

  • When I open my ServiceNow instance URL, it takes a very long time to load and eventually displays a 504 Gateway Timeout error.
  • When I log in to the ServiceNow Developer Portal, the portal itself is also very slow to load.
  • Once the Developer Portal opens, under Manage Instance, my PDI is shown as Offline, and I only see the Refresh button.
  • I have tried clicking Refresh multiple times, but the instance never comes back online.

Troubleshooting Performed

  • Refreshed the PDI status from the Developer Portal.
  • Waited several minutes and tried again.
  • Tried accessing the instance multiple times.
  • The issue persists consistently.

Note: The instance used last : 1 day ago

Questions

  1. What could cause a PDI to remain offline ?
  2. Is this typically caused by instance maintenance, instance corruption, or a ServiceNow platform issue?
  3. Are there any additional recovery steps I can perform before requesting a new PDI or contacting ServiceNow?
  4. Has anyone experienced a similar issue, and if so, how was it resolved?

Any guidance or suggestions would be greatly appreciated.

Thank you!

7 REPLIES 7

ahoy @Tanushree Maiti,

 

based on what exactly do you suggest to terminate transaction and write about fix/background script?

The author says they cannot log in... thus what you wrote is irrelevant and only brings confusions.

 

glideFather_0-1784803983515.png

 

Could we perhaps reduce the total number of comments and focus on fewer but more meaningful ones? 


✂-----Cutting-out-the---✦AI-noise✦---All-replies-written-and-vouched-for-by-GlideFather---

Aditya_hublikar
Giga Sage

Hello @shobana_n ,

 

yes  this  same issue is faced my multiple users . But now getting this message 

Aditya_hublikar_0-1784804712208.png

 

 

After some time screen is loaded but instance went to offline .

Aditya_hublikar_1-1784804712209.png

 

 

 I think , we should wait for some time , its servicenow internal error  🙂 .Instance will  work after some time .

 

If this helps you then mark  it as helpful and accept as solution.

Regards,
Aditya

Thanks for sharing @Aditya_hublikar.

Whoever wrote that message clearly never worked at service desk 😄 There's a golden rule: never ever promise a resolution time. It said "a few minutes" but that was hours ago...


✂-----Cutting-out-the---✦AI-noise✦---All-replies-written-and-vouched-for-by-GlideFather---