Troubleshooting notification policies that stopped triggering

If your notification policy has stopped triggering for runs that previously worked, there are several troubleshooting steps you can take to identify and resolve the issue.

Common troubleshooting steps

1. Space-level access: Ensure that the notification policy is configured at the space level and has access to the space containing your stack.

2. Label-based filtering: Check if the policy includes label conditions. If so, verify that the stack has the required labels.

3. Action filtering: Confirm that the policy is not filtering out the type of action associated with the run.

4. Space inheritance: If you moved a policy from the root space to a stack space, verify that inheritance is enabled on all relevant spaces. Without inheritance enabled, stacks cannot inherit resources like notification policies from parent spaces.

Using Policy Workbench for debugging

The most effective way to troubleshoot notification policy issues is to use the Policy Workbench:

1. Add sample = true to your notification policy

2. Review the sampled events to see the actual input data being processed

3. Compare the sampled input with your policy conditions to identify mismatches

This approach allows you to see exactly what data your policy is receiving and why it might not be matching your conditions.

Additional considerations

• Verify that any webhook configurations referenced in your policy are still valid and accessible

• Check if there have been any recent changes to stack labels or configurations

• Ensure the policy is defined in the correct space relative to your stack