Riya Sinha
02/07/2025, 9:13 PMRiya Sinha
02/07/2025, 9:13 PMBeginning subflow run 'peculiar-sambar' for flow 'ingest-chrombpnet-model'
12:40:43 PM
prefect.flow_runs
Created a new engine.
12:41:29 PM
prefect.flow_runs
Reset opened connections and their results.
12:41:31 PM
prefect.flow_runs
Disposed the engine.
12:41:31 PM
prefect.flow_runs
Created a new engine.
12:43:01 PM
prefect.flow_runs
Reset opened connections and their results.
12:44:02 PM
prefect.flow_runs
Disposed the engine.
12:44:02 PM
prefect.flow_runs
Flow run failed due to timeout: TimeoutError()
12:44:02 PM
prefect.flow_runs
Finished in state TimedOut('Flow run failed due to timeout: TimeoutError()', type=FAILED)
12:44:12 PM
prefect.flow_runs
@Marvin there were no task runs how do i see what timed outMarvin
02/07/2025, 9:13 PMFlowRunTimeoutError
is raised when a flow run exceeds its defined timeout.
2. Review Flow Setup: Since no task runs were initiated, the timeout might have occurred during the flow's setup phase. Check for any operations or configurations that might be taking longer than expected.
3. Increase Timeout: If the flow setup is inherently time-consuming, consider increasing the timeout limit to accommodate this.
4. Debugging: Add logging to your flow to capture more details about where it might be spending time before timing out.
You can refer to the Prefect flow engine source code for more insights into how timeouts are handled. Additionally, ensure that you're aware of common changes and gotchas in Prefect 3.x, such as the replacement of agents with workers and other infrastructure changes.
If you need more detailed guidance, feel free to ask about specific aspects of your flow or its configuration.