Work with files

Give a file to a Bot when its task needs a document or image. Your platform must have file storage, and your client must support uploads.

Give a file to a Bot

Upload the file through your client. Wait until the upload is ready, then attach it to a message and say what the Bot should do with it. An upload on its own does not send the file to a Bot. The chosen model must support the kind of input.

Keep or delete a file

You can read and delete your own files. A Chat that refers to a file keeps it. After you delete the Chat, an unused file may be removed. Unused files normally expire after 24 hours; your platform can set another time. Keep another copy of files you need to keep.

Deleting a file makes it unavailable even in earlier messages. A Bot then sees a short note in place of its content.

OpenBot saves the deletion task in the same database transaction that hides the file. A shared workflow removes the bytes and then the file record. Failed storage calls have a saved error ID and retry after a growing delay. A restart keeps that task and its saved results. One persistent retention task finds old, unused files; each instance does not run its own deletion loop.

The data move keeps an old unfinished deletion as interrupted work. Send a new delete request to resume it with your current access. Repeated requests share the active task. A task with an unknown outside result stays stopped until its decision is resolved.

Fix an upload problem

Check the file type, size, and your storage allowance. A file that is still uploading is not ready for a message. If storage is unavailable or your client cannot upload, contact your administrator or client provider with the error.