Rules and routing

Define precise conditions

Match published select values, booleans, or bounded text patterns. Avoid rules that depend on an editable label or unvalidated arbitrary content.

Test before publishing

1. Create one synthetic request for each branch and one that should match none.
2. Confirm the stored record, selected destinations, and skipped destinations.
3. Publish the rule version only after the outcomes match the intended workflow.

External effects remain separate

A rule match schedules work; it does not prove Slack, a webhook, email, or another provider received the result.