Matthew Seligson
04/06/2022, 5:19 PMKevin Kho
04/06/2022, 5:22 PM"Does not start"
and this refers to something not leaving a Scheduled state. I think we’d need an issue for thisMarvin
04/06/2022, 5:23 PMMatthew Seligson
04/06/2022, 5:24 PMKevin Kho
04/06/2022, 5:26 PMAnna Geller
04/06/2022, 6:09 PMSubmitted
state means that the agent was able to pick up the scheduled flow run and it submitted it for execution, but something has gone wrong in the flow run deployment.
Here are some steps you may take to investigate it further:
• check the agent logs to see if anything suspicious stands out there (running an agent with the --show-flow-logs
option can show more useful output)
• verify that your execution layer is able to pull your flow run’s image e.g. if the image needs to be pulled from a container registry, make sure your container can reach the Internet and has appropriate permissions to pull the image
• verify that your execution layer has enough permissions to spin up all required resources. For instance:
◦ Kubernetes agent needs proper RBAC permissions to deploy your flow run as a Kubernetes job
◦ ECS agent needs custom task_execution_role
with permissions to describe VPCs, register a task definition and run the ECS task
• verify that your execution layer has enough capacity on the cluster to deploy your flow run.Matthew Seligson
04/06/2022, 6:15 PMAnna Geller
04/06/2022, 6:17 PMMatthew Seligson
04/06/2022, 6:21 PMAnna Geller
04/06/2022, 6:22 PM