Problem

When configuring a Confluence automation rule using the Atlassian Guard "Content scanning alert" trigger, selecting the CVV/CVC alert type prevents the rule from being saved.

Environment

Confluence Cloud Automation

Steps to Reproduce

• Navigate to Confluence Administration > Automation.
• Create a new rule using the Content scanning alert trigger.
• In the "Alert type" dropdown, select CVV/CVC.
• Attempt to save the trigger/rule.

Expected Results

The rule should save successfully, and the alert.type should be used as the identifier.

Actual Results

Workaround

The rule fails to save, and the UI may display a limited list of alert types after the selection.

Notes

Jira/JSM does not appear to be affected