Skip to content
justcrawl.io

not_found

not_found

Section titled “not_found”

HTTP status: 404 Not Found

How to fix

Section titled “How to fix”
  1. Confirm the resource ID. Job IDs, workflow IDs, and schedule IDs are UUIDs. Copy-paste from the dashboard rather than typing.
  2. Check the resource wasn't deleted. Workflows and schedules can be deleted from the dashboard; their IDs return 404 forever after.
  3. Verify you're hitting the right org. If you have multiple orgs, you may be authenticated as Org A but trying to read an Org B resource — that returns 404 (not 403) to avoid leaking the existence of cross-org IDs.
  4. For job result URLs, jobs older than the retention window are pruned and return 410 Gone, not 404 — check the status code.

What this means

Section titled “What this means”

The path resolved to a valid route, but the resource ID at the end didn't match any row in your organization. We deliberately return 404 (not 403) for cross-org access attempts so callers can't enumerate other orgs' IDs by status code.

Section titled “Related errors”
  • org_not_found — the org itself is missing or inaccessible
  • auth_org_mismatch — caller authenticated but to the wrong org
  • workflow_disabled — workflow exists but is paused

Still stuck?

Section titled “Still stuck?”

Contact support with your request_id (looks like req_01HF3JKB...). We'll check whether the resource ever existed under your org.