Skip to content
Peak Atlas

Peak Automations · Run history

Every run tells you what happened.
In words, not log lines.

The history shows each run with its trigger, steps and result. When a run stops, the reason is written in business language, for example a missing connection or an approval that is still waiting.

See your first run in Peak Automations

Illustrative example · sample data · nothing is run

EXAMPLE / LIVE PREVIEW

One check.
The fitting step.

Peak Automations / Sample flowLOCAL EXAMPLE

01 / Example value

How far did the run get?

02 / What Peak Automations showsStopped at step 2: the workspace's Slack connection is disconnected.

Reconnect it in Settings · then start the run again

Change the example value. The next step follows the check.
Sample data · nothing runs

One example. Two paths.
The check
decides the next step.Compare both paths below ↓

Two example runs

How far did the run get?

Schematic example: steps done out of 3. In the product each step shows its own status.

1 / 3/ 10Stopped
Fix the cause firstEXAMPLE PATH
Stopped at step 2: the workspace's Slack connection is disconnected.
Then

Task created, contact found, note in the Inbox.

Reconnect it in Settings · then start the run again

3 / 3/ 10Finished
Run finishedEXAMPLE PATH
Task created, contact found, note in the Inbox.

Run done · the entry stays in the history

Trust needs clarity

What the history shows, and what it does not.

01 / The existing evidence

An example, not a measurement

The runs on this page are made up. You only see your real runs in your workspace.

Peak Automations / Example pathsEXAMPLE
  1. 1 / 3/10
    Stopped at step 2: the workspace's Slack connection is disconnected.Reconnect it in Settings · then start the run again
  2. 3 / 3/10
    Task created, contact found, note in the Inbox.Run done · the entry stays in the history

02 / Your check

No replay on past data

Replaying a run on past events is planned and not available today.

4 / 1010 / 10

Compare both paths and their reasons.

03 / The clear limit

No silent retries

Peak only retries where it is safe. If it is unclear whether a step already took effect, you decide.

ExampleNothing runs

The next step

Know what your routines are doing right now.

Start Peak Automations, test your first automation and find the run in the history.

See your first run in Peak Automations
Peak Automations · Run historyWhat started it?

Illustrative example · sample data · nothing is run

Frequently asked questions

Can I see why a run stopped?

Yes. The history states the reason in business language, such as a disconnected account or an approval that is still waiting.

Can an event run twice?

No. Runs go through a queue with retries and protection against running the same event twice.

Can I replay a run on past data?

Not yet. Replaying on past events is planned.

More in Peak Automations