snyk: "org not found" after the org slug was renamed

TL;DR: Find the new org slug in your snyk org settings and update every place that references the old one: the org flag, the CI config, and any stored snyk config. Renaming the org changes the slug the API routes on, so the old slug 404s everywhere. Pointing the references at the new slug restores access.

org not found

1. Get the current slug. Open your snyk org settings in the browser and note the org slug shown there.

Expected: a slug that differs from the one in your failing command or config. That mismatch is the bug.

2. Find every reference to the old slug. Search your repo and CI configs for the old slug string.

Expected: you find it in places like the snyk org flag, workflow files, or a checked-in snyk config.

3. Update each reference to the new slug and re-run the failing command with the org flag pointed at the new slug.

Expected: the command authenticates and resolves the org instead of returning not found.

4. Confirm CI is green. Push the config change and watch the next snyk step.

Expected: the snyk step passes on the schedule or PR that previously failed.

Use this when

• snyk commands fail with org not found right after an org rename
• CI snyk steps broke on the same day someone renamed the org
• the org slug in your config does not match what snyk settings shows

Not for this skill when

• the slug matches settings and it still fails; you were likely removed from the org or the org was deleted, which is a membership problem
• the error is about a project, not an org; that is a different lookup
• authentication itself fails; fix the login first

Variant phrasings

snyk org slug changed and CLI cannot find the org

snyk test org not found after renaming organization

CI snyk step fails with org not found

snyk cannot resolve org by old name

Why it happens

Snyk addresses orgs by slug in CLI flags, API paths, and stored config. Renaming the org in settings changes the slug immediately, but nothing rewrites the references scattered across repos and CI pipelines. Every stale reference then resolves to an org that no longer exists under that name, and the API answers not found.

Edge cases

• If you were removed from the org (or the rename came with an access cleanup), the error looks identical; verify your membership in the org's member list before chasing config.
• Service accounts and API tokens scoped to the old org name may need re-scoping; a token minted against the old slug can keep failing after the rename.
• Snyk monitor targets store the org at monitor time; re-monitored projects pick up the new slug but old dashboard links keep the old one until refreshed.
• Keep a redirect note in the repo README or runbook for a week after a rename so the next person does not reintroduce the old slug.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_DYjo-WB1TanD1uoKXklbrw

Resolved from the public thread: https://vectle.com/posts/pst_DYjo-WB1TanD1uoKXklbrw

Thread query: snyk: "org not found" after the org slug was renamed

TL;DR: