Slack error exchanged_trigger_id: trigger_id was already used
Last verified against Slack API reference - chat.postMessage errors
The trigger_id was already exchanged in a previous call.What error exchanged_trigger_id means
Each trigger_id can be spent once. You already used this one, so Slack reports "The trigger_id was already exchanged in a previous call." It is documented on both views.open and views.push.
Usually the same interaction was handled twice. Typical causes: two handlers (or two deployed instances listening on the same app) matched the same action; or code calls views.open and then views.push with the same trigger. Retry wrappers that repeat views.open after a timeout also produce it, because the first call often succeeded.
If the first call succeeded, the user already sees a modal and this error is just noise. If you need a second view, push it with a new trigger from a later interaction inside the modal, or change the open view with views.update, which does not use a trigger.
What it looks like
{"ok": false, "error": "exchanged_trigger_id"}Why it happens
- Two handlers or two running instances processed the same interaction.
- views.open and views.push were called with the same trigger_id.
- A retry wrapper repeated views.open after a timeout that had actually succeeded.
How to fix Slack error exchanged_trigger_id
- 1Log every views.open call with its trigger_id to find the second caller.
- 2Make sure only one handler and one environment respond to each action_id or callback_id.
- 3Use views.update with view_id to change an open modal; views.push needs a fresh trigger from an interaction in that modal.
- 4Do not auto-retry views.open; check whether the modal opened instead.
How to stop it recurring
Treat triggers as single-use tokens: consume each in exactly one place, log it, and never pass it to a second call. Keep staging and production on separate Slack apps so two deployments never answer the same interaction. Logging each trigger_id makes a second consumer easy to find.
Official reference: Slack API reference - chat.postMessage errors. See all Slack error codes or the Slack limits and quotas.
Related codes
- expired_trigger_id: trigger_id has expiredThe trigger_id is expired.
- invalid_trigger_id: trigger_id is malformedThe trigger_id is invalid. The expected format for the trigger_id argument is…
- push_limit_reached: Modal view stack is fullError returned when the max push limit has been reached for views. Currently…
- hash_conflict: View hash does not match current stateError returned when the provided hash doesn't match the current stored value.
Error exchanged_trigger_id - quick answers
What does Slack error exchanged_trigger_id mean?
Each trigger_id can be spent once. You already used this one, so Slack reports "The trigger_id was already exchanged in a previous call." It is documented on both views.open and views.push . Usually the same interaction was handled twice. Typical causes: two handlers (or two deployed instances listening on the same app) matched the same action; or code calls views.open and then views.push with the same trigger.
How do I fix Slack error exchanged_trigger_id?
1. Log every views.open call with its trigger_id to find the second caller. 2. Make sure only one handler and one environment respond to each action_id or callback_id. 3. Use views.update with view_id to change an open modal; views.push needs a fresh trigger from an interaction in that modal. 4. Do not auto-retry views.open; check whether the modal opened instead.
Should I retry after error exchanged_trigger_id?
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.