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

I'm running into an issue with my worker implementation where it seems to immediately abort the flow due to the fact the flow shows as a pending state as shown below. It almost looks like it could be related to this <https://github.com/PrefectHQ/prefect/issues/10263|issue>, however based one the timestamps shown below it's not even taking as long as the default value of 60 seconds on the `PREFECT_API_REQUEST_TIMEOUT`.

Further context: this flow was originally an Agent/Worker implementation that I just transitioned to Worker/Work Pool. Its on our k8s infra as well