Slack API · error code

Slack error not_found: View not found

Permanent - do not retryHTTP 200Modals, Home tab & views

Last verified against Slack API reference - chat.postMessage errors

What Slack returns
Error returned when the given view_id or external_id doesn't exist.

What error not_found means

The view you tried to update no longer exists, or never did. On views.update Slack says "Error returned when the given view_id or external_id doesn't exist," and its example error response is exactly {"ok": false, "error": "not_found"}. views.push lists it too, as "the requested view can't be found."

Modals are short-lived. Once the user submits or closes one, its views are gone, so a background job that finishes after the user has closed the modal will get this error when it tries to show the result. The other common cases are identifier mistakes: passing root_view_id or previous_view_id when you meant the current view, an external_id that was never set, or IDs from another workspace.

When the modal is gone, deliver the result some other way, such as a DM or ephemeral message, instead of retrying the update.

What it looks like

POST /api/views.update
{"view_id": "VNM522E2U", "view": {...}}

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

Why it happens

  • The user closed or submitted the modal before the async update ran.
  • The wrong ID was used (root_view_id or previous_view_id instead of view.id).
  • An external_id that was never set on any view.
  • The view ID came from a different workspace or app installation.

How to fix Slack error not_found

  1. 1Use view.id from the views.open or interaction response for the view you want to change.
  2. 2Confirm the external_id was set when the view was opened, with exactly the same string.
  3. 3Set notify_on_close on the modal so your app learns when the user dismisses it.
  4. 4If the modal is closed, send the result as a DM or message instead.

How to stop it recurring

Track modal lifecycle per user: record opened views and clear them on view_submission and view_closed. Background work that reports into a modal should check that record first and fall back to a message when the modal has gone away.

Official reference: Slack API reference - chat.postMessage errors. See all Slack error codes or the Slack limits and quotas.

Related codes

Error not_found - quick answers

What does Slack error not_found mean?

The view you tried to update no longer exists, or never did. On views.update Slack says "Error returned when the given view_id or external_id doesn't exist," and its example error response is exactly {"ok": false, "error": "not_found"} . views.push lists it too, as "the requested view can't be found." Modals are short-lived.

How do I fix Slack error not_found?

1. Use view.id from the views.open or interaction response for the view you want to change. 2. Confirm the external_id was set when the view was opened, with exactly the same string. 3. Set notify_on_close on the modal so your app learns when the user dismisses it. 4. If the modal is closed, send the result as a DM or message instead.

Should I retry after error not_found?

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.