Viewing History

Every time an automation runs, Synap records what happened. You can review this history to understand what your automations are doing, verify they're working correctly, and troubleshoot when something goes wrong.

The run history view

Open the Automations page and select any automation. You'll see its run history — a list of every time it executed, with the most recent runs at the top.

Each entry shows:

• When it ran — The exact date and time
• How it was triggered — Whether it ran manually, on a schedule, from a file change, or at app launch
• The result — Whether it completed successfully, failed, was cancelled, or timed out
• How long it took — The total duration from start to finish

Run details

Click any run to see the full picture. The detail view breaks down the automation into its individual steps, showing:

• Each step in sequence — What it did, in the order it happened
• Step status — Which steps completed and which failed
• Step duration — How long each step took
• Output — What each step produced (the text Claude wrote, the data an API returned, the file that was saved)
• Errors — If a step failed, exactly what went wrong

This level of detail makes it easy to understand the full chain of events. If step three failed because a file wasn't found, you'll see that clearly — along with what steps one and two produced before it broke.

What the status icons mean

• Completed — Everything ran successfully from start to finish
• Failed — One of the steps encountered an error and the automation stopped
• Cancelled — You (or the system) stopped it before it finished
• Timeout — A step took too long and was automatically stopped

How long is history kept?

Synap keeps up to 500 run records per automation, and automatically removes records older than 90 days. This happens quietly in the background — you don't need to manage storage.

Using history to improve your automations

History isn't just a log — it's a feedback loop. If you notice an automation is failing regularly, open a recent run, read the error, and ask Claude to fix the automation. If an automation is taking too long, the step-by-step timing will show you where the bottleneck is.

Over time, your automations become more reliable because you can see exactly what's happening and iterate.