Slack error cant_delete_message: Not allowed to delete this message
Last verified against Slack API reference - chat.postMessage errors
Authenticated user does not have permission to delete this message.What error cant_delete_message means
The deletion was refused on ownership or policy grounds. chat.delete documents the description as "Authenticated user does not have permission to delete this message." As with edits, deletion rights follow authorship and workspace policy: a bot deletes its own messages; users delete theirs where settings allow; admin-level deletion of others' messages is a separate, admin-only capability. A bot asked to "clean up the channel" will hit this the moment it touches messages it did not author.
Workspace and org administrators can also restrict deletion outright (compliance-minded workspaces commonly do), in which case even your own messages may refuse to die by API. And the same neighboring conditions apply as for updates: the (channel, ts) must be exact (else message_not_found), and the channel must be active.
Design cleanup features around what the token owns. For moderation-style deletion of arbitrary messages, the app needs an appropriately privileged admin flow — an ordinary bot token will never do it, no matter which scopes you add.
What it looks like
{"ok": false, "error": "cant_delete_message"}Why it happens
- The message being deleted was authored by a different identity (user or another app).
- Workspace or org policy restricts message deletion.
- An ordinary bot token is used for moderation deletions that require admin capabilities.
How to fix Slack error cant_delete_message
- 1Verify authorship of the target message and delete with the owning token.
- 2Limit bulk-cleanup features to messages your app posted (filter history by your bot_id).
- 3For moderation use-cases, involve workspace admins or an admin-capable flow rather than a bot token.
- 4Log channel, ts, and the message author on each failure so policy denials are distinguishable from bugs.
How to stop it recurring
Track the author identity of every message your app might later delete and gate delete buttons and cleanup jobs on ownership, so the API refusal becomes unreachable in normal operation. Where compliance policies forbid deletion entirely, prefer redaction-by-edit of your own messages, and document for customer admins which retention or compliance settings the feature depends on so the limitation is discovered during onboarding rather than during an incident.
Official reference: Slack API reference - chat.postMessage errors. See all Slack error codes or the Slack limits and quotas.
Related codes
- cant_update_message: Not allowed to update this messageAuthenticated user does not have permission to update this message.
- message_not_found: No message at that timestampNo message exists with the requested timestamp.
- restricted_action: A workspace preference blocks this postingA workspace preference prevents the authenticated user from posting.
Error cant_delete_message - quick answers
What does Slack error cant_delete_message mean?
The deletion was refused on ownership or policy grounds. chat.delete documents the description as "Authenticated user does not have permission to delete this message." As with edits, deletion rights follow authorship and workspace policy: a bot deletes its own messages; users delete theirs where settings allow; admin-level deletion of others' messages is a separate, admin-only capability.
How do I fix Slack error cant_delete_message?
1. Verify authorship of the target message and delete with the owning token. 2. Limit bulk-cleanup features to messages your app posted (filter history by your bot_id). 3. For moderation use-cases, involve workspace admins or an admin-capable flow rather than a bot token. 4. Log channel, ts, and the message author on each failure so policy denials are distinguishable from bugs.
Stop debugging Slack by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.