> 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/monitoring-views-and-execution-states.md).

# Find pending, running and completed work in Monitoring

Use **Operate → Monitoring** to locate a Hyperflow execution and open its details. Choose the view that matches the work's state before searching its logs.

## Choose a view

| View                        | Use it for                                 |
| --------------------------- | ------------------------------------------ |
| Pending                     | Work waiting to start                      |
| In Progress                 | Work executing now                         |
| History / Execution History | Past executions and their recorded results |
| Schedule                    | Planned future work                        |

These views classify execution activity. A scheduled row does not show that the work has already run, and a completed record still needs its output checked.

## Locate an execution

1. Open the relevant view and search for the Hyperflow name or identifier.
2. Set a time range that includes the triggering request. Record the time zone used by the screen.
3. Refresh the list and check additional result pages if needed.
4. Open the operation details. Confirm the Hyperflow, version and timestamp before treating it as the requested run.
5. Open its logs and inspect the first action that differs from the expected behavior.

Some layouts provide **Autom List View**, **Single View** and **Queue Pool View**. Use these literal UI controls where available to switch between a list, one operation and queue-grouped work. A different view changes presentation, not the execution itself.

For a concrete Dublin example, see [trace a 401 failure](/userguide/operate-and-troubleshoot/trace-a-failed-run-to-a-401-unauthorized-action.md). For fields to retain in an investigation, see [monitor executions and retain useful evidence](/userguide/operate-and-troubleshoot/monitor-executions-and-retain-useful-evidence.md).

## Handle active work deliberately

Before using **Stop Autom**, identify the intended operation and inspect completed actions, waits and downstream requests. Stop only the authorized target. Earlier external changes may remain after the run stops.

Opening the design page from Monitoring does not mean a saved change modifies the already-running execution. Use the installed version's release and execution behavior rather than assuming a live edit.

## Expected result

You have identified one execution, its state and the action evidence needed for the next step. If no record matches, check scope, filters, time zone and whether the trigger was accepted before starting another run.

For older logs, use [Archives](/userguide/operate-and-troubleshoot/find-and-download-archived-logs.md). Configure retention separately from the act of finding or downloading an archive.

### Practise the History-to-action route first

The current Monitoring page has four headings: Execution History, In Progress, Pending and Scheduled Hyper Flows. Use Search and the relevant section before opening a log.

1\. Search for Docs - Error handling - 20261013. In the 13 October example, five controlled runs appear, with different versions or error strategies; choose the intended timestamp rather than the newest row by habit.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FTpVzNHprB3B69AOiL6hi%2Fmonitoring-error-history.jpg?alt=media" alt="Five controlled runs share the same flow name; their status, version and time identify the intended execution."><figcaption><p>Five controlled runs share the same flow name; their status, version and time identify the intended execution.</p></figcaption></figure>

2\. For the recovery-branch example, select the Failed Dev v1.0.1 run starting at 10:36:24. Open its log-detail icon, then View All Logs.

3\. Inspect the first XML parsing error and retry entries. Open the E marker to inspect Error Handling Logs, then the String Assign action’s Input/Output values. ERROR\_BRANCH\_EXECUTED is the local handler output for this run.

4\. Return to Monitoring and review the other headings. Empty Pending or In Progress results mean no matching active work is displayed under the current filters. Scheduled Hyper Flows lists planned work, not proof that the work has executed.

5\. When investigating a schedule, match the planned occurrence with a later Execution History row and its output. Do not start a new run merely because the selected filters hide the original.