Matthew Seligson04/06/2022, 5:19 PM
Kevin Kho04/06/2022, 5:22 PM
and this refers to something not leaving a Scheduled state. I think we’d need an issue for this
"Does not start"
Matthew Seligson04/06/2022, 5:24 PM
Kevin Kho04/06/2022, 5:26 PM
Anna Geller04/06/2022, 6:09 PM
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
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
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 Seligson04/06/2022, 6:15 PM
Anna Geller04/06/2022, 6:17 PM
Matthew Seligson04/06/2022, 6:21 PM
Anna Geller04/06/2022, 6:22 PM