Issue Summary

When creating a Confluence Automation flow using the "Content scanning alert" trigger, the automation does not execute if a specific Alert type is selected (e.g., "Sensitive data detection: passwords"). However, the same automation triggers correctly when the Alert type filter is left empty (i.e., "All content scanning alerts").

The Guard Detect alert itself fires correctly , the issue is isolated to the automation trigger's Alert type filtering logic.

Steps to Reproduce

1. Navigate to Confluence Admin → Automation
2. Create a new flow with the trigger: "Content scanning alert for Confluence"
3. In the trigger configuration, select a specific Alert type → "Sensitive data detection: passwords"
4. Add any action (e.g., send email, restrict page, add comment)
5. Enable the flow
6. Create/edit a Confluence page with content that contains a password pattern (e.g., password=abc123)
7. Wait for Guard Detect to fire the content scanning alert
8. Observe the automation audit log

Expected Results

• Guard Detect fires the "Sensitive data detection: passwords" alert ✅

• The Confluence automation flow with the matching Alert type filter should trigger and execute the configured action

Actual Results

• Guard Detect fires the alert correctly ✅

• The automation flow does not trigger ❌

• No errors appear in the automation audit log , the rule is simply skipped

• The same flow triggers correctly if the Alert type filter is set to "All content scanning alerts"

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available