Troubleshooting reference covering the full Secure Email lifecycle — sending, bulk sending, delivery status, and replying. Each row follows Symptom → Likely Cause → Solution, grouped by category so you can jump straight to the relevant area.
Common Issues Across Send, Bulk Send & Reply
These four issues show up in more than one flow with the same root cause — documented once here instead of three times below.
|
Symptom |
Likely Cause |
Solution |
|---|---|---|
|
"License not assigned" / "Email not entitled" message; Reply icons missing; bulk send blocked |
|
|
|
Opt-out banner blocks compose or send |
Parent record's opt-out field (mapped via |
|
|
From / Reply-To dropdown empty, missing addresses, read-only, or BCC not shown |
|
|
|
Component fails to load with a JSON error ( |
Invalid JSON in |
|
Sending Secure Email (Single Compose)
Validation Errors
|
Symptom |
Likely Cause |
Solution |
|---|---|---|
|
"To Address cannot be null" |
To is blank, or multi-select returned nothing |
Enter/select a To address; if using multi-To, confirm |
|
"Email Subject or Body cannot be null" |
Template mode with no template selected; or Custom mode with empty subject/body |
Select a template, or switch to Custom and fill subject/body; check |
|
Template/Custom radio not selected, or the wrong body section shows |
|
Set the value to |
Attachments
|
Symptom |
Likely Cause |
Solution |
|---|---|---|
|
No upload control, or file type rejected |
|
Enable the upload setting; update the accepted formats list |
|
"Total File size cannot exceed 8.5 MB" |
Combined attachments over the limit |
Remove files until under 8.5 MB |
Scheduling & Delivery
|
Symptom |
Likely Cause |
Solution |
|---|---|---|
|
No schedule toggle, or a scheduled email stays in "Created" |
|
Unhide the schedule feature if needed; confirm Schedule Time is ≤ now and the batch job is scheduled ( |
|
Error toast after Send (API/integration failure) |
Paubox credentials wrong; |
Check |
Bulk Send Secure Email
|
Symptom |
Likely Cause |
Solution |
|---|---|---|
|
Bulk screen opens with no recipients loaded |
List-view record IDs not passed ( |
Launch bulk send from a list view with records selected; confirm the list-view action passes IDs |
|
"Please fill up the required fields" |
Missing From, Reply-To, email field column, subject, or body |
Complete From, Reply-To, To email field, Subject, and Message/Template |
|
No Validation of Emails Happens |
Missing |
Update Bulk FirstName and Bulk Last name fields in the metadata for that Object. |
|
Many "Records with Missing Emails" |
Selected email field is blank on those records, or the wrong field API name was chosen |
Choose the correct email field; backfill missing emails — only valid records are sent |
|
Bulk send "succeeds" but few or no Secure Email records are created |
Only record IDs with a valid email are included in the create step |
Compare "Records with Emails" vs. missing; fix the invalid set and resend |
|
Attachment upload fails in bulk |
The bulk LWC enforces a smaller ~3 MB client-side limit ( |
Use smaller files; check the accepted formats setting |
|
Emails created but not delivered yet |
Outbound records are Created / flagged Process via Batch, waiting on |
Confirm the batch scheduler and |
Delivery Status
Status Not Updating
|
Symptom |
Likely Cause |
Solution |
|---|---|---|
|
Status stays "Created" / Delivery Status blank after send |
Status batch not running; email not in the batch WHERE clause; missing |
|
|
New outbound email never gets an early status refresh |
|
Set |
|
No parent status update while Paubox still reports "processing" |
The code intentionally skips the parent update while delivery status is processing |
Wait for the next status batch run; confirm the batch is scheduled |
|
Batch status job runs once and never reschedules |
|
Set it to a value > 0 (install default is typically 60) |
|
Status batch fails to start, or returns 0 records unexpectedly |
Invalid |
Fix the SOQL fragment in |
Status Accuracy Issues
|
Symptom |
Likely Cause |
Solution |
|---|---|---|
|
Email stuck or marked Failed after a transient error (e.g. 503/504) |
Transient error codes incorrectly treated as permanent, or not on the skip list |
Ensure |
|
Paubox shows Delivered, but Salesforce shows Failed |
Delivery status text matches a value in |
Review |
|
"Partially Delivered" vs Failed vs Delivered is unclear on multi-recipient sends |
Overall status aggregates individual recipient deliveries |
Inspect |
Manual Refresh & Environment
|
Symptom |
Likely Cause |
Solution |
|---|---|---|
|
Manual "Refresh status" (Invocable/Flow) has no effect |
Blank tracking Id or From address; callout error; status payload empty |
Verify |
|
Status/send failures only in certain orgs |
|
In production orgs, set |
Replying to Secure Email
Access, opt-out, From/Reply-To, and JSON errors for Reply are covered in Common Issues above. The items below are specific to reply threading and routing.
|
Symptom |
Likely Cause |
Solution |
|---|---|---|
|
To address is empty or wrong after Reply / Reply All |
|
|
|
Reply All still includes routing / no-reply addresses |
Address not listed in |
Add exact addresses to |
|
Expected CC recipients missing on Reply All |
Original email's |
Add CC manually if needed; verify the original message actually had CC values |
|
Reply quick action won't open / spinner runs forever |
|
|
Quick Admin Checklist
|
Check |
Where |
|---|---|
|
License + feature entitlement |
User + Features Entitlement |
|
Email Configuration metadata |
|
|
Valid mapping JSON |
|
|
Routing skip list |
|
|
Allowed domains |
|
|
API credentials & environment |
|
|
Send batch scheduling |
|
|
Status batch scheduling |
|
|
Status accuracy settings |
|
|
Tracking ID populated |
|
|
Original email data (for Reply) |
From / To / CC / Parent Id / Body |
Related Pages
-
Configuration Settings — full reference for the settings named throughout this page
-
Data Model and ER Diagrams — field reference for Secure EmailMessage and Email Recipient
-
Secure Email – Architecture & Workflow — how delivery status and threading work end-to-end
-
Automation Guide — field requirements when creating Secure EmailMessage records programmatically