Run history: reopen past results

Every tool run and chain run in a workspace is recorded on the Runs page. It is the place to find a job you did last week, check what it changed, open the files it made, or see why a file failed.

Where is my run history in Hangar?

Click Runs in the sidebar. It is the last of the four sidebar items, after Studios, Tools and Chains.

The page lists everything you have processed in the current workspace, newest first, with a count such as 11 runs at the top right. Runs are grouped by day: Today, Yesterday, then the weekday name, then the date for older runs.

12345

1. 1Filter by status
2. 2Run count
3. 3Day group
4. 4What changed
5. 5Status

If you have not run anything yet, the page reads No runs yet. Run any tool and its record lands here. How to run a tool walks through a first run.

Filter runs by status

The tabs above the list filter by outcome. All shows every run. Next to it you only see the statuses that actually occurred in this workspace, so a workspace where nothing has failed has no Failed tab.

• Complete: the run finished and made its files. A run with some failed files still counts as complete, as long as at least one file got through.
• Failed: every file in the run failed, so nothing was made.
• Cancelled: you pressed Cancel (or Esc) during a tool run, or pressed Stop twice during a chain run. Files finished before that are kept.
• Stopped: you stopped a chain run early and kept what had finished.

Pick Failed after a long batch session to see at a glance which runs need a second look.

What a run row shows

Each row is a one-line summary of the run, so you can usually find what you want without opening anything.

12345

1. 1Tool name
2. 2Files and duration
3. 3Size or format change
4. 4When it ran
5. 5Status

1. Tool name, such as PDF Compress or Image Convert, with the tool's icon.
2. Files and duration: how many files went in and how long the run took, for example 24 files in 42 seconds.
3. What changed. For a complete run of a tool that makes files smaller, this is the size change, such as 58 MB to 21 MB. For a conversion it is the format change, such as HEIC to WEBP. For other tools it is the setting you used, such as the Ambient backdrop in Beautify Shot.
4. When it ran, as a relative time: 12m ago, 2h ago.
5. Status: Complete, Failed, Cancelled or Stopped. Failed runs are shown in red.

Failed and cancelled runs show no size or format change, because there is nothing to compare.

Reopen a run to see its results

Click any row. Hangar reopens the run in its tool, or in the chain view for a chain run, with its results and previews: the queue with every file, its status and a View button, and the results panel on the right. Runs from a full-screen Studio, such as Beautify Shot, reopen that Studio instead.

Say you reopen the Image Compress run from the screenshot above. The panel reads Run complete and All 24 files compressed, shows the 37 MB saved, and lists Output size, Took and Saved to.

12345

1. 1Run complete
2. 2View
3. 3Saved to
4. 4Open folder
5. 5New run

From here you can do everything you could right after the run:

• Press View on a file to open its preview and compare the original with the output. See and compare your results explains each preview style.
• Press Open folder to reveal the output files on your computer. Where Hangar saves your files explains the folder layout.
• Press Chain another tool to send these outputs into another tool, when a compatible one exists.
• Press New run to start a fresh run of the same tool.

If a run cannot be reopened, Hangar shows a Could not open run message.

Find out why a run or a file failed

A run is marked Failed only when every file in it failed. When some files failed and others got through, the run is Complete, so the failures are easy to miss in the list. Reopen the run to see them.

In the reopened run, the panel's first line gives the split, for example 2 done · 1 failed, and a What failed box lists each failed file with its reason. The same reason is shown in red under the file in the queue.

1234

1. 12 done · 1 failed
2. 2Failed file
3. 3The reason
4. 4What failed

In this example, two PDFs from Northwind Studio compressed fine and one did not, because it was password-protected. The fix is to unlock that file and run it again. A file failed: what to check covers the common reasons and their fixes.

For a chain run, reopening shows the chain run view with its Final inspection grid, which tracks every file through every step. Read a chain run, step by step explains how to read it.

Runs belong to a workspace

Each workspace keeps its own run history, along with its own brand defaults and output folder. The Runs page shows the workspace currently selected in the sidebar, and its name appears in the line under the heading.

If you keep one workspace per client, this means a client's history stays together: every run for Northwind Studio is listed under Northwind Studio and nowhere else. To see another client's runs, switch workspaces from the sidebar. Workspaces and brand defaults explains how.

A shortcut: Jump back in

You do not always need the Runs page. The Tools home shows a Jump back in row with up to three of your most recent runs, one per tool, so a job you repeat often, like Compress PDF on this week's proofs or Convert images from HEIC, is one click away.

For anything older, or to filter by status, Runs has the full list.