Automations
Automation runs
Check what an automation did, read each step's result, and retry a failed run.
Find a run
Recent executions lists runs on an installed automation's page and on an account's Automations tab. Filter with All, Failed, or Budget used. Completed Open Pack, Wonder Pick, Claim Rewards, and Complete Missions steps have View result (the eye icon).
A Budget used run stopped because the units left in your daily budget couldn't cover its next action, even if a few remained. It isn't resumed. A scheduled install tries again at its next trigger.
Step results
| Step looks like | Meaning |
|---|---|
| Name struck through, grey reason | Skipped. The step didn't run, for example because there was nothing to do or too little time was left, and the run continued. See Blocks. |
| Stop icon, highlighted reason | Stopped. The run ended here on purpose. |
| Red cross, red error | Failed. This usually ends the run. |
A failed step followed by more steps was set to continue on error in its workflow file.
Fix a failed run
Open the run and read the error.
Fix the cause, for example by editing the workflow in the builder.
On the automation's page, select Run now for that account.
If repeated failures stopped the install, clear the stop before Run now.