An exception is a lead that didn't meet your account-level policy and was held for review. The Exceptions tab shows every one of these, who approved it, and why — in one place.
Where to find it
Go to Govern > Exceptions. It sits alongside the Policies and Evidence Pack tabs.
Reading the exceptions summary
At the top of the page, Exceptions Breakdown (Past 12 Months) gives you three totals at a glance:
- Total Leads Processed Through Policies — every lead your account-level policies have checked.
- Total Leads Which Failed A Policy — how many of those didn't meet the policy, shown as a count and a percentage.
- Total Lead Failure Exceptions — how many failed leads were released through an approved exception, again as a count and a percentage.
Use these to see at a glance how often your policy is catching records, and how often exceptions are being made to let them through anyway.
Reading the exceptions table
Below the summary, the Exceptions table lists every lead that was held and released, with:
| Column | What it shows |
|---|---|
| Lead Process ID | The processing record for this check |
| Lead ID | The lead itself |
| Campaign ID / Campaign Name | Which campaign the lead came through |
| Lead Source | Where the lead originated |
| Date | When the exception was made |
| Failed Policy | Which policy the lead didn't meet |
| Approver | Who approved the exception |
| Approval Reason | The reason they recorded |
Click Download to export the table if you need it outside the platform.
Digging into why a lead was held
Each row has two actions:
- View Lead opens the lead's full record.
- View Failures takes you straight to what failed.
Both open the Lead Data panel, which has its own tabs — Profile, Associated Campaigns, Job Details, Processr Logs, Provider Logs, Edit Data, and Notes. Two of these matter most for an exception:
- Job Details — its Policy Jobs table shows the Policy the lead was checked against, the Job Name that ran, the Outcome (Failed), the Date, and a plain-language Message explaining why (for example, Live Email Check returned a status of 'invalid'). A separate Campaign Jobs table below it shows the ordinary campaign-level QA jobs run on the lead, which are independent of your account policy.
- Processr Logs — a lower-level, timestamped log of every job that ran against the lead, including the full response from any third-party service involved (for example, an enrichment provider's error message).