<@ULVA73B9P> prefect.exceptions.PrefectHTTPStatusE...
# ask-marvin
j
@Marvin prefect.exceptions.PrefectHTTPStatusError: Client error '404 Not Found' for url 'https://api.prefect.cloud/api/accounts/25af8892-2dd8-4e0c-ba9f-0ebfbdde89d6/workspaces/ce71e0ef-fdf9-425a-bdf7-306d1e160a18/flow_runs/filter' Response: {'detail': 'Not Found'} For more information check: https://httpstatuses.com/404 An exception occurred.
m
The
PrefectHTTPStatusError
with a
404 Not Found
error indicates that a requested resource could not be found. Here are some potential causes and troubleshooting steps based on the gathered information: 1. Incorrect URL or Resource ID: The URL or ID used in the request might be incorrect. Make sure that the
account_id
,
workspace_id
, or any other ID in the URL is correct. 2. Region or Project Mismatch: In some cases, such as with GCP integration, a 404 error can occur if the region or project ID is incorrect: Link: https://docs.prefect.io/latest/integrations/prefect-gcp/cloud_run/ 3. Missing Resources in Dashboard: There have been reports where a failed job does not show up in the dashboard even though it occurred: Link: https://github.com/PrefectHQ/prefect/issues/10399 4. Work Pool Not Found: When using work pools, ensure the name specified in the setup exists: Link: https://github.com/PrefectHQ/prefect/issues/9214 For more detailed troubleshooting, you can refer to the Prefect Cloud API documentation or relevant GitHub issues. If the problem persists, consider reaching out to Prefect support with specific IDs and request details. If there are any more specific details or code snippets, I might be able to give more targeted advice.
j
not helpful