Skip to main content

Can't Access File Generated In Chat

This article covers steps that can be taken if the Code Execution tool is used to created a file but the link can not be accessed and the file can not be downloaded.

Troubleshoot generated file downloads

When Hatz successfully creates a downloadable file, it should appear in the chat, app, or workflow output as a Generated file card with a download button. Images may also preview inline.

If you only see a file name, a plain text path, or an error when opening the file, use the steps below.

Use the generated file card first

  • Look for a Generated file card in the assistant response, workflow run output, or step output.

  • Click the download button on that card instead of copying a file name from the message.

  • If your organization restricts direct downloads, you may see a Microsoft 365 save option or a locked download state instead.

If Hatz says it created a file but no generated file appears

This usually means the model described a file but did not actually create a downloadable output.

  • Turn on Auto-Tool and rerun the request. Auto-Tool selects the tools needed for file generation, including Code Execution.

  • When you upload a document file, Hatz should also bind Code Execution automatically for document work.

  • If your workspace shows manual tool selection and the generated file still does not appear, you can select Code Execution directly.

  • Ask for a real downloadable output. Example: Use Code Execution on the attached file. Save the result as report.xlsx and return it as a downloadable file.

  • For multiple outputs, ask Hatz to package them into one zip file and return that generated file.

If you see a sandbox path instead of a download link

A path such as /home/daytona/workspace/output/report.xlsx means the file exists inside the Code Execution workspace. It is not a browser URL.

  • Ask Hatz to create a downloadable file for that exact path.

  • Rerun the request with Auto-Tool on and ask Hatz to return the file as a downloadable generated file.

  • In workflows, check the run output and the relevant step output for a generated file card.

If Hatz says generated files could not be saved

Sometimes Hatz creates or attempts to create files, but one or more outputs cannot be saved for download.

  • Try generating fewer files at once.

  • Use common file types such as .docx, .pptx, .xlsx, .csv, .pdf, .txt, .png, or .zip.

  • If there are many outputs, ask Hatz to put them into one zip file.

  • If the file is very large, split the task into smaller outputs.

If the generated file link opens an error

Download failures can come from an expired file, a browser issue, network security rules, or your organization's file egress policy.

  • Refresh the page and try the generated file card again.

  • Ask Hatz to regenerate the file if the link is no longer available.

  • Try an incognito window, another browser, or another network such as cellular data.

  • If you see a browser error such as DNS_PROBE_FINISHED_NXDOMAIN, ask your IT team to allow Hatz application and file domains.

  • If direct downloads are disabled for your organization, use the Microsoft 365 save option if it is available or contact your Hatz administrator.

Domains to allowlist

If a firewall, VPN, DNS filter, antivirus tool, or secure web gateway is blocking Hatz or generated files, ask your IT team to allowlist the relevant Hatz domains:

  • *.hatz.ai

  • files.hatz.ai

  • hatz-files-prod.s3.amazonaws.com

What to send Support

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

  • Your workspace or tenant name.

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

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

  • The exact filename or sandbox path shown.

  • A screenshot of the generated file card, missing link, or browser error.

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

Did this answer your question?