> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/operate-and-troubleshoot/find-and-download-archived-logs.md).

# Find and download archived logs

Inspect archived execution records in Monitoring before looking for a downloadable archive file. The current Log Source filter and the separate Archives file-list workflow are different views. Retention periods and deletion policy belong to Log Retention settings.

### Current view: inspect archived executions

Open Operate → Monitoring, select Execution History and change Log Source from Live to Archived. Use the Hyperflow name and relevant search filters to narrow the result. All can help compare the available sources without changing retention settings.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2F2fHmRlQa4nCqzLp0qZuR%2Fmonitoring-archived-filter.jpg?alt=media" alt="Monitoring with Execution History and Log Source Archived selected for Docs - Error handling - 20261013. No Operations Found describes this filtered view, not proof that the Hyperflow never ran."><figcaption><p>Monitoring with Execution History and Log Source Archived selected for Docs - Error handling - 20261013. No Operations Found describes this filtered view, not proof that the Hyperflow never ran.</p></figcaption></figure>

The inspected test flow had no matching archived operations in this view. No archive was downloaded or restored. If the result is empty, check the selected source, filters, retention period and access before concluding that evidence is unavailable.

The file-list instructions below apply where your version and permissions expose a separate Archives page. Its archive file metadata and download controls were not established by the Monitoring filter screenshot.

## If available in your version: find an archive file

1. Open the Archives page available to your role.
2. Check **Archive Name**, **File Size**, **Expiration Date** and **Archive Date**.
3. Sort or filter the list to locate the required archive period.
4. If the table is difficult to scan, open **Customize View**, rearrange or hide columns, and choose **Apply Changes**.
5. Select the intended file's download control.

Customizing columns changes the table display, not the archive contents or retention policy.

## Check the downloaded result

Confirm the file name and size, then open it with a suitable local tool. Locate the expected execution identifier and time range before using the file as incident evidence. Keep the original archive alongside any extracted working copy.

Archived logs can contain input/output data and personal information. Store downloaded files only in an approved location, restrict access and redact unnecessary data before sharing an excerpt.

## If an archive is missing

Check the archive date, expiration date, filters and your permissions. An empty archive list does not establish that there were no executions. Review the applicable Log Retention configuration and whether archiving completed.

Do not change retention or delete files merely to make an investigation easier. Preserve required evidence before an authorized retention change. For settings and escalation information, see [monitoring and retention](/userguide/operate-and-troubleshoot/monitor-executions-and-retain-useful-evidence.md).

Expected result: you have the intended archived log file and can correlate it with the execution under investigation. If download or access fails, send **<support@autommate.com>** the archive name, date, file size, product version and exact error; omit secret-bearing log contents.

### Worked check: correlate an archive with an execution

Start with an execution identifier and time window you need to investigate. Use an existing archive; do not change retention settings to manufacture one for this exercise.

1\. If a separate Archives page is available to your role and version, locate the date range that could contain the execution. Check Archive Date, Expiration Date and file name. Otherwise begin with Monitoring → Log Source Archived as shown above.

2\. If no matching archive is listed, recheck filters and access, then ask the administrator whether archiving ran for that period. Leave the outcome as archive unavailable rather than no executions.

3\. For an available file, record its Archive Name and File Size, then use its download control. Keep the file in an approved private location.

4\. Open the downloaded archive with the appropriate local tool and search for the intended execution identifier. Match the time zone and date before using an excerpt.

5\. If the file is accessible but the run is absent, retain the archive metadata and selected period for investigation. Share only a redacted excerpt with support.