{"version":"2.1.124","anchor":"oauth-org-not-allowed-plumbing-for-the-autonomous-progress-s","canonical_anchor":"oauth-org-not-allowed-plumbing-for-the-autonomous-progress-s","heading":"oauth_org_not_allowed plumbing for the autonomous-progress state [In Development]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.124\/e\/oauth-org-not-allowed-plumbing-for-the-autonomous-progress-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.124","markdown":"### `oauth_org_not_allowed` plumbing for the autonomous-progress state [In Development]\n\nThe new error code is fully wired through the request\/response and terminate-reason enums, but at present it surfaces only on initial-request failures. Mid-session token rotations that hit the org-disabled response still get classified as a generic `authentication_failed`. Expect mid-session detection to follow.\n\n**Evidence**\n\nEnum expansion only (search for `\"oauth_org_not_allowed\"` in the enum but not in the in-flight refresh paths)."}