Problem

Run failure error with run timing out due to taking longer than 1200 seconds to stat.

Check the run logs to see if there was long delay during code import. You may see the following error:

Ignoring a run worker that started after the run had already finished.

Possible causes

This error could indicate:

• A transient issue in Dagster infrastructure.

• That your code had a side effect at import that took an unusually long amount of time to run.

Solutions

• If you expect long import times for your code, you can increase the deployment setting for ­run start timeouts to 3600 seconds instead of the default of 1200.

• You can set up ­run retries to automatically retry failures. To only retry when the failure is for a reason other than an op failure, like a crash or an unexpected termination of the run worker, you can set the retry_on_asset_or_op_failure setting to false .