Slack API · error code

Slack error thread_not_found: Thread ts missing or invalid

Permanent - do not retryHTTP 200Message content & Block Kit

Last verified against Slack API reference - chat.postMessage errors

What Slack returns
Value for ts was missing or invalid.

What error thread_not_found means

conversations.replies could not find a thread for the ts you passed in that channel. The error table says "Value for ts was missing or invalid." The method's notes are stricter: "The channel and ts arguments are always required. ts must be the timestamp of an existing message."

Most cases come down to the wrong pair. The ts belongs to a different channel than the one you passed, the parent message was deleted, or the value was converted to a number and lost precision. Slack timestamps such as "1482960137.003543" are strings and must stay strings.

One documented edge case: the docs say this error "can also apply to the channel_leave and channel_join message subtypes, as these message subtypes cannot be threaded." A bot that tries to read replies on every message in a channel will hit it on join and leave notices.

What it looks like

GET /api/conversations.replies?channel=C123ABC456&ts=1482960137.0035

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

Why it happens

  • The ts and channel came from different conversations.
  • The parent message was deleted.
  • The ts was stored or sent as a float and lost precision.
  • The message is a channel_join or channel_leave subtype, which cannot be threaded.
  • The ts argument was empty because of a missing field in the event payload.

How to fix Slack error thread_not_found

  1. 1Log channel and ts together and confirm both came from the same event or API response.
  2. 2Keep timestamps as strings end to end, with no number conversion.
  3. 3For replies, pass the parent's thread_ts (or the parent's ts), not a reply's ts.
  4. 4Skip join/leave subtypes and other system messages before calling conversations.replies.

How to stop it recurring

Store messages as a (channel, ts) pair of strings and never split them. Filter on message subtype before treating something as a thread parent, and handle deletion events so stale parents are not queried. Keep the channel ID next to every stored ts, even in caches and queues.

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

Related codes

Error thread_not_found - quick answers

What does Slack error thread_not_found mean?

conversations.replies could not find a thread for the ts you passed in that channel . The error table says "Value for ts was missing or invalid." The method's notes are stricter: "The channel and ts arguments are always required. ts must be the timestamp of an existing message." Most cases come down to the wrong pair.

How do I fix Slack error thread_not_found?

1. Log channel and ts together and confirm both came from the same event or API response. 2. Keep timestamps as strings end to end, with no number conversion. 3. For replies, pass the parent's thread_ts (or the parent's ts), not a reply's ts. 4. Skip join/leave subtypes and other system messages before calling conversations.replies.

Should I retry after error thread_not_found?

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.