Enterprise Automation Notifications

• Timeline: Rolling out CW 31
• Impact: All Rencore Governance automation users

Summary

We’re implementing significant improvements to the Automations feature based on your feedback. These changes will affect how scheduled automations, policy violation triggers, and thresholds work.

Please review your existing automations to ensure they continue working as expected.

What’s Changing

Scheduled Automations Now Run Independently

• What’s 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 to ensure timing aligns with your needs.

Policy Violation Automations Will Trigger Repeatedly

• What’s changing: Automations will now trigger every time a policy violation is detected until it’s 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’s 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: No threshold, old automations with a configured threshold will carry this over (20%)

• Action Required: Review and configure appropriate thresholds for your automations

NEW: Automation Prioritization

• What’s new: Assign priority levels to automations to control processing order and resource allocation.

• Key points:

  • Provisioning automations maintain 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.

Need Help?

Support: Contact [email protected]