Automation Rule Failure Monitor

Forge app for detecting recurrent Jira Automation rules that stop checking in.

What it does

• Adds a native Jira Automation action named QuantMatrix Health Check.
• Records a successful heartbeat when a recurrent rule reaches that final action.
• Evaluates each monitor as PENDING, HEALTHY, LATE, MISSED, or RECOVERED based on the configured expected interval and grace period.
• Can create one Jira alert issue when a monitor first enters MISSED.
• Suppresses duplicate alerts while the monitor remains MISSED.
• Records recovery when a successful heartbeat resumes.

How to use it

1. Open the Jira Automation rule you want to monitor.
2. Add QuantMatrix Health Check as the final action.
3. Set a stable monitor key, display name, expected interval, and grace period.
4. Enable the rule.
5. Open the Automation Rule Failure Monitor dashboard to review monitor state and event history.
6. Optionally configure a Jira project and issue type for first-MISSED alerts.

Architecture and security

Runs entirely on Atlassian Forge. Monitor configuration, heartbeat timestamps, health state and event history are stored in Atlassian-hosted Forge KVS. The app has no Forge Remote, no external backend, no external heartbeat URL, no third-party analytics and no external customer-data egress.

Interactive dashboard resolver operations verify Jira global ADMINISTER permission server-side. The app does not request read:jira-work and does not read monitored Jira issue data. Jira write permission is used only for optional alert issue creation.

Support

Contact support@quantmatrixintelligence.com.