Skip to main content

Generated files could not be saved (file count limit exceeded)

Preserve available results and investigate a generated-output file-count limit.

This article covers the "Generated files could not be saved (file count limit exceeded)" message. This message concerns saving generated files, separately from uploading or validating source files.

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.

  • Uploaded inputs and generated outputs have separate limits.

  • Current size, count, retention, and download behavior can vary by product surface and file purpose.

Save results and review generated files

  1. Open the completed tool result and save the outputs you need.

  2. Check the chat’s available file controls for older generated files.

  3. Where a ready file offers removal, keep a downloaded copy before removing it from the conversation.

If the file controls are unavailable or a needed output has no working download, keep the chat and contact Support. If the error remains after removing an older output, follow the limit shown in the message.

When deleting a file may not fix it

The relevant limit can differ between chats, classic workflows, API runs and other saved items. If you continue in a new run, first identify the saved outputs and the work still needed, then supply the necessary inputs. Check the result of any send or update before repeating it.

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.

Recover the remaining file in a new chat

When a chat reaches its generated-file limit, check which outputs were saved and which are missing. In this example, a new chat creates the remaining discussion card. Open Files in the new chat and check the filename before repeating any more work.

Did this answer your question?