## TL;DR
Prove whether the campaign generated the mail before you investigate inboxes, because the break can sit in the review tool, the mail service or the reviewer mailbox rules. Check the campaign notification settings and the tool sent or system log for a sample reviewer, then check the mail system delivery record for that message, and only then look at mailbox rules and spam handling. Fix the layer where the trace stops, send a test notification to one reviewer, and confirm receipt before resending to everyone.

```text
how to fix access review notifications not sending: campaign email failed error
```

## Use this when
- Reviewers say they received no invitation or reminder for an active campaign.
- The campaign shows pending notifications or email errors in its log.
- One domain or department never receives review mail while others do.

## Not for this skill when
- Mail arrived and sits unread. That is reviewer management, not a sending fault.
- The campaign has not launched. Notifications start at launch, not at configuration.

## Steps
1. Pick one affected reviewer and confirm their email address on the identity record the campaign uses, since a stale or personal address explains individual misses. Verify: the address on record is confirmed correct or corrected.
2. Open the campaign notification settings and confirm invitations and reminders are enabled, with the right sender name and schedule for this campaign. Verify: notification settings are enabled and match the campaign plan.
3. Check the review tool log or admin view for a generated notification to the sample reviewer and record its timestamp and any send error shown. Verify: generation is proven with a timestamp, or the absence is the finding.
4. Trace that message in the organization mail system, following its delivery status to delivered, deferred, rejected or filtered, and note any policy that acted on it. Verify: the mail trace shows the message fate with a reason.
5. Fix the stopping layer: correct the tool mail integration settings, allow the sender in mail policy, or repair the reviewer mailbox rule, keeping the change as narrow as the trace justifies. Verify: the specific blocking layer is changed and recorded.
6. Send a fresh test notification to the sample reviewer and have them confirm arrival in the inbox, not only in a filtered folder. Verify: the reviewer confirms receipt in the inbox.
7. Resend the campaign notifications to the affected group, confirm a second reviewer receipt, and note the incident in the campaign evidence so late decisions are understood in context. Verify: the resend completes with confirmed receipts sampled.

## Why it happens
Campaign mail crosses three systems that each fail silently in their own way: the review tool may never generate it, the mail service may filter a bulk automated sender, or the mailbox may file it out of sight. Each layer blames the next, so a single traced message is worth more than any settings review. Once the stopping layer is known, the fix is usually small, and a confirmed test receipt prevents the classic mistake of resending thousands of messages into the same filter.

## Variants and edge cases

### reviewers did not get access review email invitation
The user phrasing. Start from one named reviewer and trace their message; do not start by resending to all.

### campaign reminder emails going to spam
The filtering phrasing. Bulk review mail often trips content or sender rules; work with the mail team on the sender reputation, not reviewer training.

### Okta or SailPoint campaign notifications not generated
The generation phrasing. If the tool log shows no generation, check campaign state and notification settings before mail systems.

Edge cases to check before closing the review cycle:
- Reminder schedules pause when a campaign is extended or edited in some tools. Recheck the reminder state after any campaign change.
- External reviewers at other companies face their mail policies too. Give them a direct campaign link as a fallback and log its use.
- A changed sender domain mid cycle invalidates allow rules. Freeze the sender identity during a campaign.

Compatibility: Access review campaign notifications in Okta, SailPoint and Entra, organization mail delivery tracing, reviewer identity records.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_iTu2vKBo1EVaKgW7QsSdPg