Guide

Troubleshooting Automation Errors

To troubleshoot errors in an automation using the “Automation Batch Page”, you will need to:

  1. Click on “Automation” on the Nav Panel.

  2. Click on the automation that isn’t behaving as expected.

    This opens the “Automation Batch Page”, where every triggered run for that automation is grouped by date using its GroupId.

  3. Look for a batch showing a status of “Error” or “Stopped”.

  4. Click on the “Batch date/time” to display every automation run for that period, including the one that failed.

  5. On the automation with the error, click the ellipses menu ([…]) and select “Show Details”.

  6. Click on the Error Message to see the full error message for that object run.

Understand Automation Run Statuses

Each run listed on the “Automation Batch Page” shows one of the following 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

  • Run exceeded the maximum duration. Each automation run is limited to 4 hours; a run still going after that ends in “Error”.
  • Daily API call limit 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.
  • Policy violation threshold reached. Automations triggered “On Policy Violation” only act on a limited share of the triggering inventory by default (20%, unless changed for that automation). If this threshold is exceeded, the automation does not run at all, and its author receives an email notification instead of an “Error” entry on the Batch Page.
If you expect an automation to touch a larger share of the inventory, ask your Customer Success Manager to review or raise the threshold on that automation.

Rerun a Failed Automation

  1. From the “Automation Batch Page”, click on the failed run to open its details.

  2. Click “Rerun Automation”.

    "Rerun Automation" only appears once a run has finished, with status "Completed", "Error", or "Stopped". While a run is "Running", you'll see "Stop Automation" instead.

When Rencore Retries Automatically

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

  1. Runs that end with status “Error” or “Stopped” are retried at the next scan.
  2. Runs stuck at status “New” for more than 24 hours are also rerun at the next scan.
Warning: If a run keeps ending in "Error" after several automatic retries, don't 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.

Last updated: 8/24/2026