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

Overview

exchanged_trigger_id is returned by views.open when the trigger_id was already used to open a view. A trigger is single-use: once it has been exchanged for a view, calling views.open with it again fails.

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

Symptoms

• The first views.open succeeds; a duplicate call with the same trigger_id fails.
• Retries after a successful open (or after a network timeout that actually succeeded) fail.
• Two code paths both try to open a modal from one interaction.

Common Root Causes

1. Opening two views from one trigger

A trigger can open exactly one root view. A second views.open (e.g. to open another modal) is rejected — use views.push instead.

2. Retrying after an apparent failure

A network timeout where the first views.open actually succeeded, followed by a retry with the same trigger_id, hits this error.

3. Duplicate event handling

The same interaction is processed twice (double-registered handler, redelivered event), each attempting to open a view.

How to diagnose

Open once, then reuse the same trigger:

# First call succeeds
curl -s -X POST https://slack.com/api/views.open \
  -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"trigger_id":"12345.67890.abcdef","view":{"type":"modal","title":{"type":"plain_text","text":"Setup"},"blocks":[]}}'
# Second call with the SAME trigger_id

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

Fixes

• Open exactly one root view per trigger. To stack more screens, use views.push (which needs its own fresh trigger_id from an interaction inside the modal) — not another views.open.
• Make handlers idempotent: dedupe on the interaction/event id so a redelivered event doesn’t open twice.
• Don’t blindly retry views.open. If it times out, check whether the view actually opened before retrying; a fresh trigger is required to try again.

What to watch out for

• views.push also consumes a trigger — each push needs a new trigger_id obtained from an action inside the current modal.
• Slack can redeliver events; guard your interaction handler against duplicates to avoid exchanged_trigger_id storms.
• This is close kin to expired_trigger_id and invalid_trigger_id; log which one you got so you fix the right cause (reuse vs timeout vs malformed).

Related

• Slack Error: ‘expired_trigger_id’
• Slack Error: ‘invalid_payload’
• Slack multi-step modal view-stack wizards