Slack error push_limit_reached: Modal view stack is full
Last verified against Slack API reference - chat.postMessage errors
Error returned when the max push limit has been reached for views. Currently the limit is 3.What error push_limit_reached means
You called views.push on a modal whose view stack is already full. Slack says "Error returned when the max push limit has been reached for views. Currently the limit is 3." The modals guide explains the count: "A modal can hold up to 3 views at a time in a view stack," and the views.push notes add that "After a modal is opened, the app is limited to pushing 2 additional views."
So it is the opened view plus two pushes. A wizard that pushes a new view for every step hits the wall on step four. So does a flow where an "Edit" button inside a pushed view pushes yet another view instead of updating the current one.
The fix is design, not retries. Use views.update to swap content within the current view for linear steps, and save pushes for real "go deeper and come back" moments where the previous view's state must survive.
What it looks like
POST /api/views.push
{"trigger_id": "...", "view": {...}}
{"ok": false, "error": "push_limit_reached"}Why it happens
- A multi-step wizard pushes a new view for every step.
- Nested edit or detail buttons push views recursively.
- Double-clicks pushed duplicate views onto the stack.
How to fix Slack error push_limit_reached
- 1Count views per modal: one opened plus at most two pushed.
- 2For linear steps, replace the current view with views.update instead of pushing.
- 3Use response_action: "update" or "push" in view_submission responses deliberately, knowing which one grows the stack.
- 4Debounce buttons that push views so double-clicks do not add extra layers.
How to stop it recurring
Sketch each modal flow as a stack before building it and keep the depth at three or fewer. Prefer one view with changing content for wizards, and reserve pushes for side tasks that return to the parent. Track the current depth in your modal state so code can choose update over push when the stack is full.
Official reference: Slack API reference - chat.postMessage errors. See all Slack error codes or the Slack limits and quotas.
Related codes
- exchanged_trigger_id: trigger_id was already usedThe trigger_id was already exchanged in a previous call.
- hash_conflict: View hash does not match current stateError returned when the provided hash doesn't match the current stored value.
- not_found: View not foundError returned when the given view_id or external_id doesn't exist.
- view_too_large: View payload exceeds 250kbError returned if the provided view is greater than 250kb.
Error push_limit_reached - quick answers
What does Slack error push_limit_reached mean?
You called views.push on a modal whose view stack is already full. Slack says "Error returned when the max push limit has been reached for views.
How do I fix Slack error push_limit_reached?
1. Count views per modal: one opened plus at most two pushed. 2. For linear steps, replace the current view with views.update instead of pushing. 3. Use response_action: "update" or "push" in view_submission responses deliberately, knowing which one grows the stack. 4. Debounce buttons that push views so double-clicks do not add extra layers.
Should I retry after error push_limit_reached?
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.