Hey y'all, has anyone experienced this? If the ecs job is pending for more than 120 seconds, I get a crashed alert when I go to the UI, and I see the flow started 2m18s late, yet the flow is completed. How can I extend this timeout?
RuntimeError: Timed out after 120.82966995239258s while watching task for status RUNNING
08/24/2023, 7:25 PM
I think I have. If you have a large docker image, it can take a while for the container to spin up. In the ECS block or whatever we're supposed to use these days, there should be a timeout setting. I would bump that up.
For my ECS block from months ago this field is "Task Start Timeout Seconds"
08/25/2023, 1:52 PM
That worked, Thanks @James Gatter, for some reason I did not see that while setting up my block.
08/28/2023, 1:30 PM
I didn't either! It's not at the top of the settings list so Prefect had to point it out to me. Glad it solved your problem too!