Claire Herdeman09/08/2021, 3:07 PM
is supported", the next scheduled flows will continue to fail until I restart the agent
, but it never says that the deployment has been completed
Deploying flow run 9f8a7552-90f8-49d2-8091-31db5e7ed1f3 to execution environment...
to avoid this with certainty. There is no guarantee just by using the ECSRun that an ECS Agent will pick it up. So it just seems that both the Local Agent and ECS Agent are polling and the Local Agent happens to pick it up. I think there is a race condition happening here with two agents that can pick up the flow, which is why you see that log. Either way, I would expect adding labels to the flow and agent would fix this.
Claire Herdeman09/08/2021, 3:16 PM
Claire Herdeman09/08/2021, 3:19 PM