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

Overview

already_reacted is returned by reactions.add when the calling user (your bot) has already added that exact emoji to the message. Slack won’t add a duplicate reaction.

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

Symptoms

• Reaction automations log already_reacted on messages the bot has already marked.
• The error clusters when Slack redelivers events (retries), causing the same handler to run twice.
• Adding a different emoji to the same message succeeds.

Common Root Causes

1. Duplicate event delivery

Slack retries event deliveries if your endpoint is slow to ack. A “react to this message” handler that isn’t idempotent runs twice and the second reactions.add fails.

2. Re-processing history

A bot that scans channel history and reacts can revisit messages it already reacted to.

3. Concurrent workers

Two workers pick up the same message and both try to add the same emoji.

How to diagnose

Add the same reaction twice:

curl -s -X POST https://slack.com/api/reactions.add \
  -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"channel":"C0123456789","timestamp":"1700000000.000100","name":"white_check_mark"}'
# Repeat the identical call

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

Check current reactions to confirm the bot is already present:

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

Fixes

• Treat already_reacted as success. The desired end-state (the emoji is present) is already true; don’t error or retry.
• Dedupe events: track the Slack event_id / X-Slack-Retry-Num header and skip work you’ve already done.
• Ack fast: respond 200 to the Events API within 3 seconds so Slack doesn’t redeliver in the first place.
• Check before adding with reactions.get if you want to avoid the call entirely.

What to watch out for

• Reacting is idempotent by intent — design handlers so a duplicate is a no-op, not an alert.
• already_reacted is per-user: the error only fires if your bot already reacted, not if a human used the same emoji.
• Don’t confuse it with too_many_reactions (per-user cap) or too_many_emoji (distinct-emoji cap on the message).

Related

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