This article covers the "Generated files could not be saved (file count limit exceeded)" message. This message is about generated output persistence, which is separate from ordinary upload or source-file validation.
What this means
Hatz can save generated outputs from chats and other product runs so you can download them later. A workspace item, chat, or run can only retain a limited number of generated output files. If that generated-output limit is reached, the AI response may still complete, but one or more generated files may not be saved or linked for download.
Uploads and generated files are different
Uploaded or source files are files you attach for Hatz to read, such as PDFs, spreadsheets, images, transcripts, or source documents.
Generated files are files Hatz creates as output, such as reports, spreadsheets, documents, images, archives, or code artifacts.
A file type can be supported for upload without guaranteeing that every generated output can be saved indefinitely in the same chat or run.
Current size, count, retention, and download behavior can vary by product surface and file purpose.
How to reduce generated files in Chat
Download any generated output you want to keep before removing it.
Open the chat's file or source panel from the attachment area.
Find older generated files you no longer need in that chat.
Use the delete action shown for a ready generated file to remove it from the chat file list and context.
Deleting a chat-generated file removes that file from the current chat context and queues it for cleanup. Keep your own downloaded copy if you need to preserve it outside the chat.
When deleting a file may not fix it
Deleting generated files is currently a chat recovery path. It may not resolve file-count or persistence limits for workflow runs, API runs, workspace items, or generated outputs that are not visible in the chat file panel. For those cases, start a new run if practical and contact Support with the run link if the issue repeats.
How to avoid hitting the limit
Start a new chat or run for a distinct task instead of continuing a long-running generation thread.
Download final outputs and remove older generated versions once you no longer need them in context.
Ask for fewer generated variants at once when creating many documents, images, or files.
For source-file issues, use the Supported File Types article and in-product error messages as the source of truth.
When to contact support
If you still see this message after reducing generated files or starting a new run, contact Support. Include the chat URL, workflow run URL, workshop item URL, or API request ID when available, plus the approximate time and timezone, output file types, how many files were generated, and the exact message you saw.