How Do I Deal With "Stuck Status" Warnings?

Occasionally, you may encounter the following warnings for a build:

• GATSBYDIAGNOSTICSTUCKSTATUSTIMEOUT
• GATSBYWATCHDOGSTUCKSTATUSTIMEOUT

The GATSBYDIAGNOSTICSTUCKSTATUSTIMEOUT is a diagnostic log that prints whenever a build has been running for a specified amount of time, but no process updates have been reported.

Eventually, GATSBYWATCHDOGSTUCKSTATUSTIMEOUT will terminate the build if there continues to be no process updates.

The default timeout periods are:

• 5 minutes for GATSBYDIAGNOSTICSTUCKSTATUSTIMEOUT
• 30 minutes for GATSBYWATCHDOGSTUCKSTATUSTIMEOUT

For larger sites (e.g. those that need to source many nodes from a CMS), these default times may be too aggressive. To control when diagnostics are logged and when the process should terminate, you can specify timeout periods using the following environment variables:

• GATSBY_DIAGNOSTIC_STUCK_STATUS_TIMEOUT - the time interval to wait before logging a detail message if no status updates occur
• GATSBY_WATCHDOG_STUCK_STATUS_TIMEOUT - the time interval to wait before terminating the build if no status updates occur

The environment variable values are set in milliseconds. If you want to specify that the build should terminate after 1 hour then you should set GATSBY_WATCHDOG_STUCK_STATUS_TIMEOUT to 3600000 milliseconds.

If the build continues to terminate due to GATSBYWATCHDOGSTUCKSTATUSTIMEOUT after increasing the timeout period, there may actually be something wrong and you should contact support.