İçeriğe geç
Peak Atlas

Peak Automations · Monitoring

Spot problems before they find you.
One health status per automation.

Peak Automations rates every active automation: did the recent runs finish, is a connection missing, do two rules contradict each other, could a loop occur? Whatever needs your attention sits at the top.

Check the health of your automations

Illustrative example · sample data · nothing is monitored

EXAMPLE / LIVE PREVIEW

One check.
The fitting step.

Peak Automations / Sample flowLOCAL EXAMPLE

01 / Example value

How healthy is this automation?

02 / What Peak Automations showsTwo automations keep switching the same task between done and open.

Look at the conflict · adjust one rule or pause it

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 states

How healthy is this automation?

Schematic scale from 0 to 10 for illustration. In the product the status lists its reasons one by one.

4/ 10Attention
Check the hint firstEXAMPLE PATH
Two automations keep switching the same task between done and open.
Then

The recent runs finished and every connection is in place.

Look at the conflict · adjust one rule or pause it

9/ 10Healthy
Keep it runningEXAMPLE PATH
The recent runs finished and every connection is in place.

Nothing to do · the status stays visible

Trust needs clarity

What monitoring does, and what it does not.

01 / The existing evidence

An example, not a measurement

The status on this page is made up. Only your workspace shows how healthy your automations are.

Peak Automations / Example pathsEXAMPLE
  1. 4/10
    Two automations keep switching the same task between done and open.Look at the conflict · adjust one rule or pause it
  2. 9/10
    The recent runs finished and every connection is in place.Nothing to do · the status stays visible

02 / Your check

No self-healing

Peak does not repair an automation on its own. Automatic fixing is planned and not available today.

4 / 1010 / 10

Compare both paths and their reasons.

03 / The clear limit

A hint, not an intervention

Peak shows the hint and its reason. Pausing, changing or reconnecting is your call.

ExampleNothing runs

The next step

Calm, because you know what is running.

Start Peak Automations and see the health status of your first tested automation.

Check the health of your automations
Peak Automations · MonitoringDoes it finish?

Illustrative example · sample data · nothing is monitored

Frequently asked questions

Does Peak detect conflicts between automations?

Yes. Peak flags when two automations change the same object in opposite ways or when an automation could trigger itself again.

Does Peak repair an automation on its own?

No. Peak shows the hint and its reason. Self-healing is planned; today you decide.

What is the status based on?

On recent runs, connections and permissions, and on conflicts and loops with other automations.

More in Peak Automations