Enterprise automation notifications

In 2025 we changed how scheduled automations, policy violation triggers and thresholds work, based on customer feedback. This notice announced the change in July 2025. It has since rolled out to all customers and is kept as a record of what changed.

The behaviour it describes is how automations work today. For the current steps, see Create a custom automation, which covers priority and the threshold limit. Automations created before the change may need the review steps listed under each change.

Who is affected

• Rolled out: Calendar week 31, 2025
• Impact: All Rencore Governance automation users

What changed

Scheduled automations now run independently

• What is changing: Scheduled automations will now run on their configured schedule, regardless of scanning job completion.
• Previous behavior: Automations waited for same-day scanning jobs to complete.
• New behavior: Automations run according to the schedule. If an automation for an object is still running, it will not be triggered again.
• Action Required: Review all scheduled automations and check that their timing fits your needs.

Policy violation automations will trigger repeatedly

• What is changing: Automations will now trigger every time a policy violation is detected until it is resolved.
• Previous behavior: Automations triggered once per violation.
• New behavior: Automations trigger repeatedly for unresolved violations (unless a previous automation is still in progress).
  • Example: A Teams channel with fewer than 2 owners will trigger notification emails after each scan until the issue is resolved.
• Action Required:
  • Review automations triggered by policy violations.
  • Add resolution actions or appropriate delays to prevent excessive notifications.
  • Consider implementing automated fixes rather than just notifications.

Enhanced threshold configuration

• What is changing: Threshold settings are now more flexible and located in the automation configuration (Details step).
• New capabilities:
  • Set custom thresholds as percentages or absolute numbers.
  • Automations stop processing after reaching the threshold (rather than not starting at all).
  • Default setting: new custom automations start with a threshold of 20%. You can change it or clear it to run without a limit.
• Action Required: Review and configure appropriate thresholds for your automations.

New: automation prioritization

• What is new: Assign priority levels to automations to control processing order and resource allocation.
• Key points:
  • Provisioning automations keep the highest priority (cannot be changed).
  • Customize priorities based on your business needs.
  • Avoid setting all automations to the highest priority.
• Action Required: Assign appropriate priorities to existing automations.

What you need to do

1. Review your scheduled automations and their timing.
2. Review automations triggered by policy violations and add resolution actions or delays.
3. Review and configure the thresholds of your automations.
4. Assign priorities to your existing automations.

If you need help, contact [email protected].