Budget caps and auto-pause

No objectives, just a cap

Autopilot has no goal, KPI, or objective field. You cannot tell it to hit a target and let it optimize toward it, because there is nothing in it that optimizes. The one real control for an unattended task is money, and it takes the shape of a standing credit cap.

When you create the task you can enter an optional budget cap in credits. The dialog says plainly what it does: it pauses the autopilot when spend crosses that number. Leave it blank and the task runs with no ceiling, which is fine for a small test but risky for anything you might forget about.

What actually costs credits

Most of an autopilot's spend is the planning call, the step that arranges your creatives across the calendar. Scheduling the organic posts themselves is free. So the cap is really guarding against the task firing again and again, running up planning calls while you are not watching.

Two safety gates

Two gates protect a task that runs on its own. The first is the budget gate. Before each fire, the engine checks spend against your cap, and if spend has reached it, the task pauses and reads as paused over budget rather than spending another credit.

The second is the failure gate. If a task fails three times in a row, the engine disables it automatically. A broken task does not keep hammering away forever.

Pick a cap you could wake up to

Treat the cap like the cash you would hand a teenager for a night out: the most you are happy to see spent before you check back in. You can always raise it, or recreate the task, once you have watched a cycle or two run clean.