Getting notified about errors

REDA Connect 1.94000 includes automatic email notifications for newly created Connect Logs needing attention. Administrators choose recipients by enabling Connect Error Notifications on their User records. The checkbox is off by default; installing or upgrading does not subscribe everyone.

Enable notifications: add Connect Error Notifications to the administrator’s User layout. Go to Setup → Users → Users, edit each intended active recipient, select the checkbox and save. Check Salesforce email deliverability and the recipient’s email address. In Setup → Custom Metadata Types → REDA Connect Config → Manage Records, C011 controls notifications (1 enables; 0 disables), and C012 limits recipients per log (default 50). See the layout guide. The list view and optional report subscription below remain useful for monitoring unresolved items.

Part 1 — The list view you check on a cadence

Build the Unresolved Connect Logs list view exactly as described in Reading and working with Connect Logs: a view on the Connect Logs tab filtered to Resolved Date Time equals (blank).

In this release, new and updated error logs can carry Attention Needed. A view with a blank Resolved Date Time remains useful for unresolved work. Inspect Process and Exception to distinguish errors from informational webhook receipts.

Then make checking it a habit:

• Daily for orgs actively messaging customers.
• Each morning and after every bulk send for high-volume orgs.
• Pin it: on the Connect Logs tab, select the view, click the pin icon next to the view name. It becomes the tab's default view, so the open items greet you every time you open the tab.

Expected result: an empty view means nothing is waiting; any row is an open item to triage.

Part 2 — A subscribed report that emails you

A Salesforce report subscription runs a report on a schedule and emails you the results — and it can be told to email only when there is something to show. That turns the passive list view into an active notification.

Step 1 — Create the report

1. Open the Reports tab (App Launcher → Reports).
2. Click New Report.
3. In the category search, type Connect Logs and select the Connect Logs report type, then click Start Report.
4. In the report builder:
   • Under Filters, set Show Me to All connect logs and the date filter (Created Date) to All Time.
   • Click Add filter…, choose Resolved Date Time, operator equals, leave the value blank, and click Apply. The report now shows only unresolved logs.
   • Under Outline, add the columns Connect Log Number, Process, Exception, Failed Records, and Created Date.
5. Click Save & Run. Name it Unresolved Connect Logs, and save it into a private or shared report folder you own — packaged folders are read-only, so choose or create your own (for example Messaging Operations).

Expected result: the report lists the same rows as your list view — every unresolved log.

Step 2 — Subscribe to it

1. Open the saved report, click the ▾ (down arrow) at the top right of the report, and choose Subscribe.
2. In the Edit Subscription window:
   • Schedule: Frequency Daily (or Weekly on selected weekdays), pick a time your team is at their desk — for example 8:00 AM.
   • Conditions: click Add conditions to this report, then set: Aggregate Record Count, Operator Greater Than, Value 0. This is the key step — with this condition, Salesforce only sends the email when at least one unresolved log exists.
   • Recipients: yourself by default; click Edit Recipients to add the rest of your admin team (they must have access to the report's folder).
3. Click Save.

Expected result: on schedule, Salesforce runs the report; if there are unresolved logs, the recipients get an email with the report results and a link to open it. Quiet days produce no email.

Worked example

You subscribe your two admins daily at 8:00 AM with the Record Count Greater Than 0 condition. Tuesday, a bulk send has three failures overnight and writes a log; at 8:00 both admins receive "Unresolved Connect Logs: 1 record". One admin opens the log from the email, fixes the cause, sets Resolved Date Time, and Wednesday morning no email arrives — silence now genuinely means all clear.

FAQ

Where to go next

• Reading and working with Connect Logs — what each field means and the resolved-date triage workflow the routine above depends on.
• A message isn't sending — what to do with the failures your new subscription surfaces.
• Troubleshooting index — the master symptom → fix table.