Help Centre › Building Processes
When a run doesn't succeed, Automize tells you how it didn't succeed, because the fix is different in each case. The two outcomes you'll see are Rejected and Failed, shown as distinct badges in your run history.
1. Rejected – it never started
A rejected run was stopped by a pre-run check before any step executed. Nothing happened, so there's nothing to undo – you just need to clear the blocker and run again. Common reasons include:
- Bot busy – the chosen bot is already running something.
- Insufficient credits – there aren't enough credits to start the run.
- Preflight failed – a startup check didn't pass (for example an input file that no longer matches its expected structure).
- Missing activities – the process has no steps to run.
- Circular process – the process refers back to itself in a way that would loop forever.
2. Failed – it started, then hit a problem
A failed run started normally but a step errored partway through. Because work may already have happened, it's worth checking what completed before the failure. To find the cause:
- Open the run in Run History and read the step log to see which step failed and why.
- Check the Insights tab for advisories the bot raised about the run.
- If the value in a field looks like an error code such as
#VAR!or#VALUE!, see Formula errors and the sentinels in Working with variables in RPAs.
To make a step recover from transient failures on its own, see Retries and continue-on-fail; to route a failure down its own path, see Error handling and Try-Catch.