Lesson 7 of 10 · 5 min
Budgets, limits, and safety settings
Set per-run and monthly credit budgets, quiet hours, and error handling, and know what pauses a live workflow on its own.
Video walkthrough coming soon
Autopilot
Open workflow settings
Open the menu in the top bar and choose Settings. These settings apply to every run of this workflow.
Credit budgets
- Credit budget per execution. The most one run may spend. Before each AI step, Pinnora checks what the run has spent so far plus what the step will cost. If that would pass the budget, the step stops and the run fails with a budget error.
- Monthly credit budget. The most the workflow may spend on AI steps in a month.
- Pause when a budget is reached. Turn this on and the workflow unpublishes itself when it hits a budget, and the project is notified.
The daily fee is separate. It does not count against these budgets.
Pick a monthly budget you would be fine seeing spent if you forgot about the workflow for a few weeks. You can always raise it later.
Timing
- Timezone. Schedules use the project's timezone unless you set another one here.
- Quiet hours. A start and end time when scheduled runs do not fire. Use this to keep posts out of the middle of the night.
- Timeout workflow. The longest a run may take before it is stopped.
What gets saved
You choose whether to keep data for failed runs, successful runs, and test runs. Keep executions for sets how many days that data stays, up to 30. After that it is removed.
Error handling
- Error workflow. Pick another workflow in this project that starts with On workflow error. It runs whenever this one fails, so you can send an alert to Slack or email.
- Retry on fail. In any node's settings, turn on retries and set how many tries and how long to wait between them.
- On error. Each node can stop the workflow, continue, or send the error down a separate output that you handle yourself.
Three failures in a row
If a live workflow fails three times in a row, Autopilot unpublishes it and notifies the project. A broken workflow does not keep retrying. Fix the cause, test it, and publish again.
Approvals for risky steps
For anything you want a person to check, add Send and wait for response before it. The run pauses until a teammate approves or rejects. The Winner detected to new ad set and Approve then publish templates both work this way. You can also add a Budget gate node to stop a run when spend reaches a limit you set at that point in the flow.