PDI Instance Frequently Hibernating and Showing 504 Error After Instance Upgrade

Akshay Kumar11
Tera Contributor

Hello Team,

After upgrading my PDI to the latest release, the instance frequently goes into hibernation. When I click "Start Building", I often receive a 504 Gateway Timeout error, and after refreshing the page, it sometimes loads as a blank screen.

Could you please investigate and help resolve this issue?

Thank you.
Akshay Kumar.

1 ACCEPTED SOLUTION

Dr Atul - LNG
Tera Patron

Hi @Akshay Kumar11 

 

PDI Maintenance and Availability

Some PDIs may be temporarily unavailable due to scheduled maintenance.

 

If your PDI is currently offline, you can:

 

Wait for maintenance to complete and your instance to become available again.

 

Release your current instance and request a new one. Please note that releasing your instance will permanently delete all data and work stored on it.

 

As a reminder, PDIs are unsupported development resources and do not have an availability, support, or uptime SLA. We strongly recommend regularly backing up any work you don’t want to lose.

View solution in original post

3 REPLIES 3

Dr Atul - LNG
Tera Patron

Hi @Akshay Kumar11 

 

PDI Maintenance and Availability

Some PDIs may be temporarily unavailable due to scheduled maintenance.

 

If your PDI is currently offline, you can:

 

Wait for maintenance to complete and your instance to become available again.

 

Release your current instance and request a new one. Please note that releasing your instance will permanently delete all data and work stored on it.

 

As a reminder, PDIs are unsupported development resources and do not have an availability, support, or uptime SLA. We strongly recommend regularly backing up any work you don’t want to lose.

Akshay Kumar11
Tera Contributor

Hi @Dr Atul - LNG,

I waited and my instance came online, but the issue is still occurring. Whenever I reload or access the instance, it intermittently shows 502/504 Gateway errors, and the instance becomes unavailable again.

Agree, it's very common issue nowdays and team is working to sort this out. We have patience that's only key here buddy