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.

Prefect Community

image.png

How are others handling the occasional ECS/Fargate error `Timeout waiting for network interface provisioning to complete.` ?

We have created an AWS support request asking if there is a way for ECS to automatically retry the task. (Or increase the timeout might be helpful too!)

We are not using the prefect lazarus process.

There was <https://prefect-community.slack.com/archives/CL09KU1K7/p1646927556698999?thread_ts=1646922911.889629&amp;cid=CL09KU1K7|another thread> that reported that and unfortunately it seems like there is not much that can be done because the AWS docs literally says to restart it manually. On the Prefect side, you could try an automation?

<@U01QEJ9PP53> Reading the automation docs, an automation can only respond to a change in prefect state. The problem is, prefect shows the task as "running". Which means prefect will not be able to respond to a change in state. Correct me if I'm wrong.

I have created <https://github.com/PrefectHQ/prefect/issues/5561|this bug report> regarding the lack of state change.

So we chatted internally about this last night and this has to do with the Zombie Killer currently being unreliable so we’re working on a fix for that to make it better so that this failure will be detected