Skip to main content

Troubleshooting Triggers

Troubleshooting Triggers​

Trigger not activating for severity-based conditions

Verify you are using numeric string values for severity (for example, severity = '0' for SEV0:Critical, not severity = 0 or severity = 'SEV0'). Check that you are using supported comparison operators (=, !=, CONTAINS, DOES_NOT_CONTAIN) and not numeric operators (>, <, >=, <=) which do not work with string fields.

Trigger with severity greater than condition does not work

Severity values are stored as strings, not numbers. You cannot use > or < operators with severity. To trigger on multiple severity levels (for example, SEV0 or SEV1), create separate conditions with severity = '0' and severity = '1', then set the match type to Match Any (OR).

Trigger not activating for any incidents despite correct configuration

Verify trigger conditions match actual event data. Check the incident type selected in the trigger matches the incidents you are creating. Test triggers with realistic scenarios before deployment. Review the trigger execution logs for error messages.

Trigger activating too frequently or causing performance issues

Optimize trigger conditions and reduce evaluation frequency. Add more specific conditions to narrow the trigger scope. Consider using Activity Updated frequency only when necessary, as it evaluates on every field change. Review and refine conditions regularly based on trigger execution patterns.

CEL trigger condition syntax error when saving

Check for common CEL syntax errors: use == for comparison not =, close all strings with matching quotes, use correct field names (case-sensitive), ensure boolean expression returns true or false. The error message indicates the position of the syntax error. Verify field names match exactly: incident.severity not incident.severiy.

CEL trigger condition does not activate even though condition seems correct

Verify the CEL expression returns a boolean (true/false), not a value. Check that field names match exactly (case-sensitive). Add null checks for fields that may not always be present: incident.owner != null && incident.owner == "value". Test the condition with actual incident data. Check execution logs for runtime errors.

CEL trigger runtime error: No such field

The field you are referencing does not exist or is null. Verify the field name is spelled correctly and exists in your incident or alert type. Add null safety checks before accessing custom fields. Check that you are using the correct namespace: incident. for incidents, alert. for alerts.

Next steps​

info

Need Help? Contact our support team by email at support@harness.io or visit the Harness Documentation for additional resources and troubleshooting guides.