File Manager: user guide, limits, and error messages

What it is

Browsing files and folders in File Manager — How the file list or folder tree might look in your app.

Each bot has its own storage area -- files from one bot never appear in another's. Upload one file or many, work with nested folders, rename and move things around. Typical contents are documents, images, and attachments that the scenario needs to hold between steps.

Who can use it

Team roles or bot access settings — Team and roles, or a role limited to file access, depending on your setup.

Not everyone gets access to this storage by default. You need either a full bot role (owner or admin) or a dedicated file manager role -- the exact name depends on the product. Add the person to the right bot and assign one of these roles.

If someone only needs to work with files and not the rest of the bot configuration, a files-only role is sufficient -- provided that role exists in the product and fits your access policy.

Limits

Storage by tariff (total size per bot)

The number below is the whole bucket for that bot: every file in File Manager, one running total.

Tariff	Max storage (per bot)
Free	500 MB
Full	3 GB
Premium	10 GB
Professional	100 GB
Unlimited	300 GB

Fixed product limits (all tariffs)

These limits apply regardless of plan.

Rule	Value
Maximum size of a single file	50 MB
Maximum number of files in one folder	1 000
Maximum subfolders under one parent	50
Maximum depth of the folder tree	5 levels
Maximum length of a title (file or folder name field)	500 characters
Name search: maximum results returned	10
Search by type + name: allowed range and table page size	Between 1 and 100; list page size 50

Possible issues and what to do

Match what you see on screen to the first column, then read across for the cause and the fix.

Access

Error message	What it means	What to do
Access denied	Most often: wrong role, wrong bot, a different component, or this bot simply does not have File Manager turned on yet.	Check that the user has the right role, that they are added to the correct bot, and that File Manager is turned on for that bot. Only work with files and folders you have access to.

Single-file upload

Error message	What it means	What to do
Invalid or missing file. Send multipart/form-data with field "file".	No file actually arrived, or the upload step was skipped -- for example nothing was chosen in the file picker.	Open the file selection window, pick a file, confirm, and try again. Make sure you actually attach one file before sending.
File size must not exceed 50 MB.	File is larger than the hard limit.	Shrink, split, or compress the file; stay within 50 MB.
File is required	A file was required, but nothing was sent -- often the user did not select a file when uploading.	Pick a file in the file selection window, confirm, and submit again.
Validation error from the form	One of the form checks did not pass -- wrong folder, invalid value in a field, or something similar. The message text points to the specific problem.	Read the full message and correct what it points to (folder, name, or other field).
File manager storage quota exceeded.	Total storage for this bot would go above the limit for your plan.	Delete files, upload a smaller one, or switch to a plan with more space.
Maximum 1000 files per folder	The folder already holds the maximum number of files.	Free space in that folder, use another folder, or delete old files.
Upload source file is not readable	The system could not read the file during transfer -- temporary glitch or a bad file source.	Try the upload again from a normal file on your device. If it keeps happening, contact support.
Could not read upload file size	The file disappeared or could not be read right after you chose it.	Upload again. If the error repeats, try another file or another browser.
Upload size mismatch (declared X, file Y)	Two numbers in the message: what was reported and what actually arrived -- something went out of sync.	Start the upload again with the same file, or pick the file from disk again so size and content match.
Content for upload cannot be empty.	Nothing was sent to upload, or the content was empty.	Choose a real, non-empty file and send the upload again.
Upload source is not readable: path	The system could not read the file from its source -- network drive, special location, and similar.	Save a copy to your device and upload that copy, or try a different file location.
Upload source is empty or size could not be determined.	The file is empty, broken, or could not be measured.	Choose another file or export the document again, then upload.
Form validation rule error	A form field rule was not met -- name too long, file too large, or something else. The message names the exact field or limit.	Shorten the name, reduce size, or follow what the on-screen message says (for example up to 500 characters for the name, file under the size limit).

Multi-file upload

Error message	What it means	What to do
No files. Send multipart/form-data with field "files[]" (recommended) or "files".	No files reached the server -- most often no files were chosen in the upload window, or the selection was not confirmed.	In the file picker, select one or more files and confirm, then run the upload again. Without a choice in the dialog, the system has nothing to receive.
Validation error from the form	A form check failed -- target folder, file name, or another field. The error text points to what needs fixing.	Fix what the error message points to and try again.
At least one file is required	The upload had no files attached -- same idea as nothing selected when choosing files.	Add at least one file in the file selection step, then send again.
One or more files are invalid.	At least one file failed the basic check (type, size, or a broken file).	Choose the files again; if one is huge or unusual, try smaller files or another format.
Each file size must not exceed 50 MB.	At least one file is over the limit.	Upload smaller files (each under 50 MB).
Access denied	Same as in the access table above.	Adjust roles, bot, and File Manager, and work only with what your access allows.
Maximum 1000 files per folder	Target folder is full.	Use another folder or remove some files first.
File manager storage quota exceeded.	Same as a single file upload: you would go over the plan's storage cap.	Free space on the bot or move to a plan with a higher limit.
Other error message	The cause is likely one of those covered in the single-file table: bad input, folder at capacity, or an unreadable file.	Find the same message or the closest one in the single-file table above and follow that row.

Folders: create and move

Error message	What it means	What to do
Access denied	No access, or the resource is not in your space.	Check roles, bot, File Manager, and that the folder is yours to change.
Maximum directory depth is 5 levels	You cannot create or move a folder so the tree is deeper than five levels.	Flatten the structure a bit, or place the folder under a higher-level parent that stays within the limit.
Maximum 50 directories per folder	That parent already has 50 subfolders.	Create new folders under a different parent, or remove some subfolders first.
Cannot move directory into itself	New parent is the same as the item you are moving.	Choose another parent folder.
Cannot move directory into its descendant (would create a cycle)	You are trying to put a folder under one of its own subfolders.	Move it to a folder outside that sub-tree.
Directory cannot be moved into itself	Same situation as "into itself," with different wording in the app.	Do not pick the same folder you are moving as its new parent.
New parent directory must be in the same component	The parent you chose belongs to another bot or another file area.	Pick a parent that lives in this bot's File Manager only.
Cannot move directory into its descendant	Shorter phrasing for the "cycle" case.	Do not place the folder inside one of its own subfolders.

Moving files (same file-count limit)

Error message	What it means	What to do
Access denied	Same as in the access table.	Apply the same steps as for "Access denied" above.
Maximum 1000 files per folder	The destination folder is full.	Delete or move some files, or pick another destination folder.

"Not found" and wrong selection

Error message	What it means	What to do
File not found	No such file anymore, the link is outdated, or you are not allowed to see it. This is not the same as "no files" during upload -- that is about nothing being selected in the picker. Here the system is looking for a file that should already be stored.	Open the file list again, pick a file that is still there. If the file was removed, upload it again.
Directory not found	There is no such folder, or you cannot see it -- wrong bot, deleted, or no access.	Choose a folder that appears in the tree for this bot, or create one first.
FileComponent not found	File Manager is not connected to this bot yet.	Turn on or add the File Manager component for that bot, then return to the file screens.

①What it is

②Who can use it

③Limits