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

:wave: I'm facing an odd issue that just came up across all my prefect workers I run in Kubernetes. No changes were made but my prefect-workers are crashlooping with this error: `prefect.exceptions.PrefectHTTPStatusError: Client error '404 Not Found' for url '<https://api.prefect.cloud/api/accounts/>&lt;accountID&gt;/workspaces/&lt;workspaceID&gt;/work_pools/'`

For anyone else that lands here. This was the issue:
1. User API Key was used for the worker
2. User was deleted from prefect cloud
3. API Key still worked with the `/health` endpoint as described here: <https://discourse.prefect.io/t/prefect-worker-pod-fails-with-error-405-method-not-allowed/2739/4>
4. Confirmed API key belonged to user with this endpoint `<https://api.prefect.cloud/api/me/>`
5. Created new API key with service account
6. restarted workers in kubernetes namespace
7. connection was successful/healthy now
Not sure why an API key would still be operational after a user was deleted.....