The automations list: failures and the spending limit per run
How to read each row in Automations, what each failure reason means and how the spending limit per run works.
A row
- The apps the automation uses — up to three logos, and “+N” when there are more
- The name and the schedule in words, with the next run
- The last 7 runs as dots, with a written summary: how many were ok, how many failed, how many were skipped
- When something is wrong, a third line gives the reason and the way out
The colors
The automation is running fine.
The last run failed.
Skipped for lack of balance, or stopped at the spending limit. Not a fault in the automation.
The failure reasons
| On screen | What to do |
|---|---|
| Skipped, no balance | The balance did not cover the expected cost. It runs again when there are credits; the owner decides on buying |
| Stopped at the spending limit | The run went over the spending limit per run. Check what it did and, if that is normal, use Adjust the limit |
| {app} disconnected | An app the automation uses went down. Use Reconnect; it runs again at the next scheduled time |
| The {key} key is no longer accepted | A key saved in Secrets was refused. Replace its value in Secrets |
| It ran, but could not deliver | The notice, email or calendar event did not go out. Open the run to see where it stopped |
| Prophet error | A failure on our side talking to the model. It usually clears on the next run |
| Timed out | The run took too long — an automation run stops at 30 minutes. Split the request or make the instruction more direct |
| The Worker did not finish | The Worker stopped without finishing. Open the run’s conversation to see why |
| Reason not identified | Open the run and, if it is still unclear, use Ask for help |
The automation panel
Click the row to open the panel: What happened (the reason and the way out), What it does, Last runs — each opens the conversation with what Prophet did — and Schedule. What happened also holds Ask for help, which opens a ticket about that automation.
Spending limit per run
It lives under Schedule, in the automation panel:
The default. Prophet works out the limit from the cost of that automation’s last completed runs; with no history, it uses a starting value.
Write how many credits a run may spend. Clearing the number goes back to automatic.
Applies on top of any limit. If you write more than the plan allows, the panel tells you which limit is in effect.
In a team
An automation’s limit can only be changed by whoever created it. Actions that involve money — buying credits, adjusting the limit — do not show for team members; the owner is notified.