Slack error file_not_found: File could not be found
Last verified against Slack API reference - chat.postMessage errors
Could not find the file from the upload ticket.What error file_not_found means
Slack could not resolve the file you referenced. The wording depends on the method. On files.completeUploadExternal it is "Could not find the file from the upload ticket." On files.info it is "Value passed for file was invalid," on files.delete "The file does not exist, or is not visible to the calling user," and on chat.update "One or more of the provided file IDs could not be found."
For bots, the upload flow is the usual source. The ID returned by files.getUploadURLExternal has to be completed with files.completeUploadExternal, and the docs say that method "can only be called once"; if it is never called, "the uploaded file and associated metadata will be discarded." Completing with a mistyped ID, an ID from a different workspace, or an upload whose bytes never reached the upload_url will fail here.
Outside uploads, the file may have been deleted, or it is not visible to your token, for example a file in a channel the bot cannot see.
What it looks like
POST /api/files.completeUploadExternal
{"files": [{"id": "F123ABC456", "title": "report"}], "channel_id": "C123ABC456"}
{"ok": false, "error": "file_not_found"}Why it happens
- files.completeUploadExternal was called with an ID that did not come from files.getUploadURLExternal in the same workspace.
- The bytes were never successfully POSTed to upload_url before completing.
- The file was deleted before it was referenced.
- The file exists but is not visible to the calling token.
How to fix Slack error file_not_found
- 1Pass the exact file_id returned by files.getUploadURLExternal to files.completeUploadExternal.
- 2Check that the POST to upload_url returned HTTP 200 before completing.
- 3Use the same token and workspace for every step of the upload.
- 4For existing files, confirm with files.info and check that the bot can see where the file was shared.
How to stop it recurring
Run the three upload steps inside one function with one token, and stop if the byte upload is not HTTP 200. The official SDK helpers (filesUploadV2 in Node, files_upload_v2 in Python) handle the sequence for you. Log the file_id at each step so a broken handoff between steps is easy to spot.
Official reference: Slack API reference - chat.postMessage errors. See all Slack error codes or the Slack limits and quotas.
Related codes
- access_denied: Access to a requested resource is deniedAccess to a resource specified in the request is denied.
- file_upload_size_restricted: File too large for workspace upload policyThe size of provided file is too large, as the team has restricted uploads of…
- file_uploads_disabled: Workspace has disabled file uploadsTeam has disabled all file uploads.
- method_deprecated: The method has been deprecatedThe method has been deprecated.
Error file_not_found - quick answers
What does Slack error file_not_found mean?
Slack could not resolve the file you referenced. The wording depends on the method.
How do I fix Slack error file_not_found?
1. Pass the exact file_id returned by files.getUploadURLExternal to files.completeUploadExternal. 2. Check that the POST to upload_url returned HTTP 200 before completing. 3. Use the same token and workspace for every step of the upload. 4. For existing files, confirm with files.info and check that the bot can see where the file was shared.
Should I retry after error file_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.