https://prefect.io logo
Join Slack
Powered by
<@ULVA73B9P> ECS worker log shows a scheduled flow...
# ask-marvin
j
@Marvin ECS worker log shows a scheduled flow run without deployment:
Copy code
Flow run 32847291-0ce5-4701-97e4-5a825d1fb647 did not pass checks and will not be submitted for execution
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/prefect/client/orchestration/_deployments/client.py", line 765, in read_deployment
    response = await self.request(
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/prefect/client/orchestration/base.py", line 53, in request
    return await self._client.send(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/prefect/client/base.py", line 354, in send
    response.raise_for_status()
  File "/usr/local/lib/python3.12/site-packages/prefect/client/base.py", line 162, in raise_for_status
    raise PrefectHTTPStatusError.from_httpx_error(exc) from exc.__cause__
prefect.exceptions.PrefectHTTPStatusError: Client error '404 Not Found' for url '<https://api.prefect.cloud/api/accounts/><obscured>/workspaces/<obscured>/deployments/aa906b52-eb02-44fc-926e-e788656701a6'
Response: {'detail': 'Deployment not found'}
For more information check: <https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404>
How can a flow run be scheduled without a deployment?
m
Your message was too long by 36 tokens...
Your message was too long by 12 tokens...
Your message was too long by 2 tokens...
The error you're encountering occurs when a flow run is scheduled without an existing deployment, which results in a "404 Not Found" error. This typically happens when the deployment associated with the flow run is deleted or not properly registered, but a flow run is still scheduled based on previous configurations. Here's a brief overview of how deployments work in Prefect 3.x: - Deployments are server-side representations of flows, storing metadata necessary for remote orchestration, such as schedules and infrastructure configurations. They allow for remote execution and scheduling of flows. Prefect Deployments Overview From the information gathered, there are a couple of potential causes and solutions: 1. Deleted or Missing Deployment: It's possible that the deployment for the flow run was deleted or not created properly. Ensure that the deployment exists and is correctly configured. 2. Configuration Issues: Check the configuration of your deployment, particularly the API and workspace settings, to ensure they match the expected setup. 3. Infrastructure Changes: If there have been changes to the infrastructure or work pools, ensure these are reflected in the deployment configuration. For further troubleshooting, you might want to verify the deployment status and configurations through the Prefect API or UI, ensuring that all necessary metadata and infrastructure settings are in place. Additionally, reviewing any recent changes to your Prefect setup might help identify the root cause. If you continue to face issues, you may want to explore the GitHub issues for similar cases or consider reaching out to the Prefect community for more tailored support.
2 Views
Open in Slack
PreviousNext
Powered by