Hey Prefect - I keep getting these errors when a flow is scheduled with my ECSTask block.
Copy code
State message: Submission failed. RuntimeError: Timed out after 120.81494164466858s while watching task for status {until_status or 'STOPPED'}
Can I handle this somehow? is this handled by the
task_start_timeout_seconds
?
r
Ryan Peden
11/16/2022, 3:22 AM
It looks like it is timing out because the ECS task hasn't entered the RUNNING status after 120 seconds (the default value for (
task_start_timeout_seconds
).
Increasing the timeout value is a good starting point. 120 seconds may not always be enough, depending on the size of image you are using.
If that doesn't help, checking the stopped tasks for errors might reveal more about what is happening.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.
