Lesson 7 of 8 · 4 min

Monitor a running autopilot

Read a task's status, next and last run, and spend, and pause or resume it from the Autopilot list.

The autopilot list

Every task you create shows up on the Autopilot tab as a row, and the row is built to be read in a second. It tells you when the task will next run, when it last ran, and how that last run turned out. A task you have paused shows as paused instead of a next run time.

The spend bar

If you set a budget cap, the row carries a spend bar, credits used against the cap, like the fuel gauge on a car. It stays neutral while you have headroom, turns amber once you pass eighty percent, and turns red at the cap. That color change is your early warning that the budget gate is about to pause the task. With no cap set, the row simply shows total credits spent.

Reading the last status

The last-run status says what happened on the most recent fire. A healthy task reads ok. A task that hit its ceiling reads paused over budget. And if a task keeps failing, remember it disables itself after three failures in a row.

Pausing and resuming

Each row has a pause control. Pausing stops future fires without deleting the task or its settings, and resume picks it back up on its normal cadence. Reach for pause when you want to change direction, since the inputs freeze at creation and the clean way to change them is to pause the old task and build a new one.

What you will actually see today

This surface is live, but it is new. If your project has no autopilots yet, the tab is empty by design, and nothing here populates until you create your first task. So an empty tab is not a bug, it just means you have not started one.

Reference

Keep going