Skip to main content

Can't Access File Generated In Chat

Find saved generated outputs and distinguish missing files, save failures and download problems.

Troubleshoot generated file downloads

When Hatz successfully creates and saves a downloadable output, it appears as a Generated file card in the chat, app response, workflow run, or step output. The card can include Download, Save to Microsoft 365, or Preview, depending on the file and your organization settings.

Use the file card rather than a filename or path written in the assistant's message.

Expanded Files list showing a generated Cedar text file, its size and download action.

If no Generated file card appears

The model may have described a file without creating a downloadable output, or Code Execution may not have been enabled for that message.

  • Check the completed tool step or workflow output first. If a saved result exists, use its file control. If a file was created but no download was returned, ask Hatz to return that existing file before regenerating it.

  • In chat, turn on Auto-Tool and resend your request. If you select tools manually, leave Auto-Tool off, select Code Execution, and resend.

  • Ask for an actual downloadable output. Example: Use Code Execution on the attached file. Save the result as report.xlsx and return the generated file.

  • For many outputs, ask Hatz to package them into one zip file.

  • In a workflow, check both the overall run output and the relevant step output.

If you see a sandbox path

A path such as /home/daytona/workspace/output/report.xlsx, /mnt/data/report.xlsx, or outputs/report.xlsx points to a file inside the Code Execution workspace. It is not a browser download link.

  • Ask Hatz to return the file at that exact path as a downloadable generated file.

  • Keep Auto-Tool or Code Execution enabled when you resend the request.

  • Do not ask Hatz to save directly to a local path such as C:\Users\name\Downloads or /Users/name/Desktop. Download the Generated file card or use Microsoft 365 when available.

If Hatz reports a file status or reference problem

  • Still processing: wait briefly, then retry. Repeated immediate retries will not make processing finish faster.

  • Could not be processed or extraction failed: re-upload the source file. If it fails again, try a smaller file or a common supported format.

  • More than one attached file has the same name: remove the duplicate attachment, rename one file, or clearly identify the file you want Hatz to use.

  • File is not attached: attach the correct source file to the current chat or start a new chat with the file.

  • Generated files could not be saved: follow the exact error. For a file-count error, see the file-count-limit guide. Save accessible outputs and identify which files are missing.

If the Generated file card will not download

  • Stay signed in to the same Hatz workspace and open the chat or run that contains the file card.

  • Refresh the page and use Download on the card again. Do not copy an old file URL from the browser or assistant message.

  • If the file is no longer available, check the task’s completed work before asking to regenerate only the missing output. Keep the original chat and inputs so you can continue from the same work.

  • Try an incognito window or another supported browser. If your organization restricts downloads, use Save to Microsoft 365 when available or contact your Hatz administrator.

  • If the problem only occurs on a corporate network, test another network such as cellular data. Ask your IT team to allow your Hatz workspace and *.hatz.ai. Normal Generated file card downloads remain within the signed-in Hatz experience; only add another hostname when the browser's error or Hatz Support identifies it.

What to send Support

If the issue continues, email [email protected] with:

  • Your workspace or tenant name.

  • The chat, app, workflow run, or step link where the file was generated.

  • The date, time, and time zone of the attempt.

  • The exact filename, visible status, error message, or sandbox path.

  • A screenshot of the Generated file card or browser error, with sensitive information removed.

  • Whether the same download works in another browser or network.

Before repeating a send, update or code execution, check its result in the connected app or completed tool step. Use the output attached to the relevant tool step; a filename in a reply is not a download.

Watch: Find and download a generated file

Reopen a completed chat, download the intended workbook and review its separate preview.

Did this answer your question?