Slack API · error code

Slack error cannot_reply_to_message: This message type cannot have thread replies

Permanent - do not retryHTTP 200Message content & Block Kit

Last verified against Slack API reference - chat.postMessage errors

What Slack returns
This message type cannot have thread replies.

What error cannot_reply_to_message means

You passed a thread_ts to chat.postMessage (or chat.postEphemeral) that points to a message which cannot start a thread. Slack says "This message type cannot have thread replies." The parent exists, but its type does not allow replies.

System messages are the usual cause. The conversations.replies docs state that channel_join and channel_leave subtypes "cannot be threaded," and bots that reply to "the latest message" in a channel often pick one of these up. A related mistake is threading under a reply: the thread_ts argument docs say to "Avoid using a reply's ts value; use its parent instead."

This is different from thread_not_found (the parent cannot be found) and from restricted_action_non_threadable_channel, where threading is blocked for the whole channel rather than for one message.

What it looks like

POST /api/chat.postMessage
{"channel": "C123ABC456", "thread_ts": "1700000000.000100", "text": "Update"}

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

Why it happens

  • thread_ts points to a channel_join, channel_leave or other system-subtype message.
  • The bot picked the newest message in a channel as a thread parent without checking its subtype.
  • A reply's ts was used as thread_ts instead of the parent's.
  • The parent is a message type that Slack does not allow to be threaded.

How to fix Slack error cannot_reply_to_message

  1. 1Fetch the parent and inspect its subtype before replying.
  2. 2When replying to a reply, use its thread_ts (the parent) as your thread_ts.
  3. 3Skip system subtypes when choosing a message to thread under.
  4. 4If no valid parent exists, post a new top-level message and thread future updates under it.

How to stop it recurring

Have your bot thread only under messages it posted itself, and store their ts at post time. That avoids guessing parents from channel history, which is where system messages slip in. When you must thread under someone else's message, check its subtype first and skip system messages.

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

Related codes

Error cannot_reply_to_message - quick answers

What does Slack error cannot_reply_to_message mean?

You passed a thread_ts to chat.postMessage (or chat.postEphemeral ) that points to a message which cannot start a thread. Slack says "This message type cannot have thread replies." The parent exists, but its type does not allow replies. System messages are the usual cause.

How do I fix Slack error cannot_reply_to_message?

1. Fetch the parent and inspect its subtype before replying. 2. When replying to a reply, use its thread_ts (the parent) as your thread_ts. 3. Skip system subtypes when choosing a message to thread under. 4. If no valid parent exists, post a new top-level message and thread future updates under it.

Should I retry after error cannot_reply_to_message?

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.