🚨 Slack Error: 'too_many_reactions' — Cause, Fix, and Troubleshooting Guide

Overview

too_many_reactions is returned by reactions.add when the calling user has reached the maximum number of reactions they may add to a single message. Slack caps how many reactions one user can place on one item.

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

Symptoms

• A bot that adds several status emoji to a message fails after a few.
• Only the last few reactions.add calls on the same message fail.
• Reacting to a different message works fine.

Common Root Causes

1. Bot adds many reactions to one message

Status/voting automations that pile several emoji onto the same message hit the per-user cap.

2. Accumulated reactions over time

A long-lived message the bot keeps annotating gradually reaches the limit.

3. Retry loops adding reactions

A buggy retry adds new emoji instead of recognising the desired ones are already present.

How to diagnose

Inspect how many reactions the bot already placed:

curl -s "https://slack.com/api/reactions.get?channel=C0123456789&timestamp=1700000000.000100" \
  -H "Authorization: Bearer $SLACK_BOT_TOKEN"

{"ok": true, "message": {"reactions": [{"name": "eyes", "users": ["U0BOTBOT01"]}, {"name": "hourglass", "users": ["U0BOTBOT01"]}]}}

A growing list all owned by your bot user (U0BOTBOT01) explains the cap.

Fixes

• Use fewer, meaningful reactions. Pick one or two emoji that convey state (e.g. ✅ done) rather than a whole palette.
• Replace, don’t accumulate: on a state change, reactions.remove the old emoji before adding the new one.
• Consolidate signalling into a threaded message or a Block Kit status field instead of many reactions.

What to watch out for

• The limit is per-user per-message; using a single clear status emoji sidesteps it entirely.
• too_many_reactions (this user’s cap) is distinct from too_many_emoji (the message’s distinct-emoji cap across all users).
• If you use reactions as a state machine, prune stale states with reactions.remove so you never approach the ceiling.

Related

• Slack Error: ‘ratelimited’
• Slack Error: ‘msg_too_long’
• Reaction-driven Slack automations for ops