Run Timeout Issues

Run Timeout Limit Reached

Understanding Timeout Limits

1. Public Worker Pool Timeout
   For security reasons, Spacelift enforces a default timeout limit of 70 minutes on runs running on the public worker pool. This limit helps prevent potential abuse and resource overconsumption.

2. Private Worker Pool Timeout
   If you’re using a private worker pool, you have control over the timeout duration. You can set a custom timeout by configuring the SPACELIFT_LAUNCHER_RUN_TIMEOUT environment variable. This allows longer-running tasks to complete without interruption.

   • For more details on configuring this environment variable, refer to the Spacelift documentation on worker pool configuration.

Troubleshooting Steps

To address timeout issues, consider the following options:

• Adjust Timeout on Private Workers
  For private workers, you can set SPACELIFT_LAUNCHER_RUN_TIMEOUT to a higher value if your task consistently requires more than the default limit.

• Optimize or Split Your Stack
  If a single stack run is approaching the timeout limit, consider splitting your stack into smaller, more manageable parts. This can improve efficiency and reduce the risk of timeouts.

• Check Efficiency
  Review your configuration and code to ensure there are no unnecessary delays or inefficiencies. Removing redundant steps can help the run complete within the allotted time.