Slack error team_added_to_org: Workspace migrating to an Enterprise organization
Last verified against Slack API reference - chat.postMessage errors
The workspace associated with your request is currently undergoing migration to an Enterprise Organization. Web API and other platform operations will be intermittently unavailable until the transition is complete.What error team_added_to_org means
Slack is moving this workspace into an Enterprise organization (Enterprise Grid), and the Web API is temporarily refusing work for it. The docs say platform operations "will be intermittently unavailable until the transition is complete." The neighboring org_login_required carries a similar message: "The workspace is undergoing an enterprise migration and will not be available until migration is complete."
Nothing in your request is wrong, and it is scoped to one workspace. If you serve many tenants, only the migrating one fails, which is a useful way to tell this from a global outage or from invalid_auth. Treat it as a temporary state: queue and retry with backoff instead of disabling the installation.
Once the migration finishes, look at the workspace again. Enterprise organizations bring org-level installs and policies, and your app may need re-approval or produce new errors such as team_access_not_granted.
What it looks like
{"ok": false, "error": "team_added_to_org"}Why it happens
- The customer's workspace is being migrated into an Enterprise organization.
- Calls arrived during the migration window, when Web API access is intermittent.
- A multi-workspace app hit one tenant mid-migration while others kept working.
How to fix Slack error team_added_to_org
- 1Confirm the failures are limited to one team_id; if so, treat them as a migration, not an outage.
- 2Pause and queue work for that workspace, retrying with exponential backoff.
- 3Do not revoke tokens or mark the install as uninstalled because of this error.
- 4After the migration, call auth.test and check whether the app needs admin approval at the org level.
How to stop it recurring
Handle errors per tenant: give each workspace its own retry queue and circuit breaker so one migrating customer cannot stall others. Alert when a workspace stays in this state for an unusually long time, and contact the customer's admin rather than guessing.
Official reference: Slack API reference - chat.postMessage errors. See all Slack error codes or the Slack limits and quotas.
Related codes
- team_access_not_granted: Token not granted access to this workspaceThe token used is not granted the specific workspace access required to…
- service_unavailable: Service temporarily unavailableThe service is temporarily unavailable
- internal_error: Transient error on Slack's sideThe server could not complete your operation(s) without encountering an error,…
- invalid_auth: Authentication cannot be validatedSome aspect of authentication cannot be validated. Either the provided token…
Error team_added_to_org - quick answers
What does Slack error team_added_to_org mean?
Slack is moving this workspace into an Enterprise organization (Enterprise Grid), and the Web API is temporarily refusing work for it.
How do I fix Slack error team_added_to_org?
1. Confirm the failures are limited to one team_id; if so, treat them as a migration, not an outage. 2. Pause and queue work for that workspace, retrying with exponential backoff. 3. Do not revoke tokens or mark the install as uninstalled because of this error. 4. After the migration, call auth.test and check whether the app needs admin approval at the org level.
Can I retry after error team_added_to_org?
Yes - this is a retryable condition. Back off (start around one second and double on each attempt, with jitter) and watch for a retry-after hint from the platform before resending.
Stop debugging Slack by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.