Slack API · error code

Slack error user_disabled: Specified user has been disabled

Permanent - do not retryHTTP 200Channels, membership & DMs

Last verified against Slack API reference - chat.postMessage errors

What Slack returns
A specified user has been disabled.

What error user_disabled means

You asked conversations.open to start a DM or group DM with a user whose account is deactivated. Slack says "A specified user has been disabled." The ID is valid; it just belongs to someone who no longer has an active account.

This is a data freshness problem, not a code bug. Employee directories, CRM mappings and on-call rotations keep user IDs long after people leave. A bot that DMs "the owner" of a ticket or the next person on call will start failing when the stored owner is deactivated. It differs from user_not_found, where the ID does not resolve at all.

Other methods report deactivated users in their own way. users.lookupByEmail, for example, returns users_not_found for a deactivated user and suggests using users.list to find them. Either way, the fix is to pick a different, active recipient.

What it looks like

POST /api/conversations.open
{"users": "U0123ABCDEF"}

{"ok": false, "error": "user_disabled"}

Why it happens

  • The target user was deactivated after their ID was stored.
  • An on-call or ownership mapping still points to a departed employee.
  • A group DM list includes one deactivated user among active ones.

How to fix Slack error user_disabled

  1. 1Call users.info for the stored ID and check the deleted flag on the user object.
  2. 2Remove or replace deactivated users in ownership, routing and on-call tables.
  3. 3For group DMs, drop the disabled user and retry with the remaining IDs.
  4. 4Fall back to a team channel or a backup owner when the primary recipient is disabled.

How to stop it recurring

Subscribe to the user_change event or re-check stored users periodically, and flag routing rules that point at deactivated accounts. Every DM-based workflow should have a fallback recipient so offboarding never silently drops alerts. Log which rule pointed at the disabled user so the owner of that mapping can update it.

Official reference: Slack API reference - chat.postMessage errors. See all Slack error codes or the Slack limits and quotas.

Related codes

Error user_disabled - quick answers

What does Slack error user_disabled mean?

You asked conversations.open to start a DM or group DM with a user whose account is deactivated. Slack says "A specified user has been disabled." The ID is valid; it just belongs to someone who no longer has an active account. This is a data freshness problem, not a code bug. Employee directories, CRM mappings and on-call rotations keep user IDs long after people leave.

How do I fix Slack error user_disabled?

1. Call users.info for the stored ID and check the deleted flag on the user object. 2. Remove or replace deactivated users in ownership, routing and on-call tables. 3. For group DMs, drop the disabled user and retry with the remaining IDs. 4. Fall back to a team channel or a backup owner when the primary recipient is disabled.

Should I retry after error user_disabled?

No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.

Stop debugging Slack by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.