Troubleshoot automation errors

Find out why an automation failed and run it again. The Automation Batch Page groups every run of an automation by date and shows the full error message of each failed run.

Before you begin

• Your Rencore role includes the Read Automation permission. Owner, Admin, Contributor and Reader have it. See Rencore roles.

Steps

Find the error

1. Click Automation on the Nav Panel.
2. Click the automation that is not behaving as expected. The Automation Batch Page opens, where every triggered run of the automation is grouped by date using its GroupId.
3. Look for a batch with the status “Error” or “Stopped”.
4. Click the Batch date/time to show every automation run for that period, including the one that failed.
5. On the run with the error, click the ellipses menu ([…]) and select Show Details.
6. Click the error message to see the full error message for that object run.

Rerun a failed automation

1. On the Automation Batch Page, click the failed run to open its details.
2. Click Rerun Automation. It only appears once a run has finished, with the status “Completed”, “Error” or “Stopped”. While a run is “Running”, you see Stop Automation instead.

What you see

Each run on the Automation Batch Page shows one of these statuses: New (queued, not yet started), Running (in progress), Completed (finished successfully), Error (failed during execution) or Stopped (halted manually or by the system before finishing).

A run stuck at New for more than 24 hours is treated like a failure: Rencore Governance reruns it automatically during the next scan, the same as it does for Error and Stopped runs.

Common causes of automation errors

• The run exceeded the maximum duration. Each automation run is limited to 4 hours. A run still going after that ends in “Error”.
• The daily API call limit was reached. Actions that call Microsoft 365 APIs (for example, disabling a user or updating permissions) can fail once the automation’s daily API call allowance is used up.
• The threshold limit was reached. Automations triggered “On Policy Violation” or “On Schedule” stop processing new objects for the day once they reach their Threshold limit (20% for new custom automations). Objects started before the limit are still processed, and Rencore Governance emails the recipients of the Thresholds in Automation notification. The objects above the limit do not show up as “Error” on the Batch Page. If you expect an automation to touch a larger share of the inventory, open the automation, go to the Details step and raise or clear its Threshold limit.

When Rencore retries automatically

Rencore Governance also retries some failed runs without any action on your part:

• Runs that end with the status “Error” or “Stopped” are retried at the next scan.
• Runs stuck at the status “New” for more than 24 hours are also rerun at the next scan.

If it does not work

If a run keeps ending in “Error” after several automatic retries, do not keep waiting on the automatic retry. Contact your Customer Success Manager or [email protected] with the automation name and the Batch date/time of the failing run, so support can investigate the underlying cause.