Routing exception resolutions
An exception records that a channel's chosen location and your rules disagreed. The hint was honoured; the exception is the note of where your rules would have differed. Background in when a channel disagrees.
The resolutions
| Resolution | What it means |
|---|---|
| Accepted the channel's choice | The channel was right. Your rules are the thing out of step |
| Overrode to the rules | Your rules were right, and the channel's hint should not have won |
| Tuned the rules | The disagreement was genuine and you changed your rules because of it |
| Other | None of the above. Use the notes to say why |
Each resolved exception keeps who resolved it and when.
Reading the pattern rather than the row
One exception rarely tells you much. The distribution does.
Mostly accepted the channel's choice — the channel understands its own fulfilment better than your rules do. Either bring the rules into line, or leave that channel honouring its hints and stop treating the difference as noteworthy.
Mostly overrode to the rules — the channel is sending hints that do not reflect reality. The fix is on the channel side: consider switching it to run the rules instead. See channel settings fields.
Mostly tuned the rules — working as intended. This is the queue doing its job, and it should get quieter over time.
The queue should shrink
A steadily falling open count means your rules are converging on how fulfilment actually happens. A stable or rising one means the same disagreement keeps recurring and nothing has been changed to address it.
Notes
Each exception carries a free-text note. Worth using: the reasoning behind a resolution is what makes the pattern readable months later, and a queue of bare resolutions loses most of its value as feedback.