@Marvin I’m trying to run a flow on a push-work-pool worker ( ECS fargate). getting this error at the start of the run:

Flow run could not be submitted to infrastructure: An error occurred (InvalidParameterException) when calling the RunTask operation: No Fargate configuration exists for given values.

but then the run continues somehow. the issue is checking all the clusters/services and containers on AWS ECS and comparing the logs, I couldn’t find where the flow is running on my infra?!

You're saying that you got an error about

No Fargate configuration exists for given values.

but your flow run keeps going and you can't find it running on your infrastructure. Ok, let's dig in! First, to help you better, can you tell me which version of Prefect you are using?

@Marvin 2.x

Here's what I found regarding your issue: 1. ECS Fargate Configuration: Ensure your ECS task definition includes: -

task_definition["cpu"]

and

task_definition["memory"]

set to string values. -

task_definition["requiresCompatibilities"]

must include

"FARGATE"

. -

task_definition["networkMode"]

should be

"awsvpc"

when using Fargate. Reference: Prefect ECS Guide. 2. Infrastructure Issues: It's noted that dynamically provisioning infrastructure with work pools, like ECS, has specific requirements which might lead to various complexities. Reference: Prefect Flows Configure Infrastructure. 3. Task/Service Discovery: Since you mentioned logs and instances not matching, it might be that the flow is reusing an existing task definition with mismatched configurations or running as a differently named task. Double-check your ECS configurations and task definitions, making sure all parameters align with the above notes. If the problem persists, consider opening an issue in the Prefect GitHub repository for further assistance. If detailed guidance is still needed, you should refer to Prefect's ECS documentation.