Last updated · May 2026
- Production-ready APIs
- SOC 2 Type I - In Progress
SECRET_NOT_FOUND
HTTP 404 with next_step=contact_support. The worker asked for a secret that isn't stored, or has been revoked.
What it means
When a worker checks out a secret it specifies workspace_id, kind, and label. If no active row matches, Core returns 404. The most common causes are:
- Connection wizard step never completed — no secret was written.
- Secret was rotated and the old label was revoked.
- Wrong workspace context propagated to the worker.
How to fix
- In the dashboard, re-run the connector setup wizard for the affected sink.
- Verify the workspace selector matches the workspace the secret was originally created in.
- If still failing, share your
request_idwith support.