Exceptions and Recovering a Failed Step

Exceptions and recovering a failed step

An exception is Codex asking a person to look at something it will not decide alone. Most are small: confirm a stop, review a bounce, reword an email. One kind, a failed step, stops a journey until its owner recovers it. This lesson covers the queue, the exceptions a representative meets most, and the four recovery actions.

Where exceptions live

Sales → Exceptions lists everything that needs a person, on three tabs: Open, Escalated, and Resolved. Your own open exceptions also appear on the Exceptions tab of the Work Queue, with the same row actions.

Each row names the exception, the prospect, the journey, the reason, the recommended action, and what was tried. A row closes when its cause is fixed.

The exceptions you meet most

Exception What it means What you do
Step Failed An automated email step failed Recover it with Retry or Skip
Send Unconfirmed Microsoft 365 did not confirm a send Check Sent Items, then Mark Sent and Continue or Mark Failed
Microsoft 365 Disconnected Your connection ended Reconnect Microsoft 365
Needs Different Wording An email repeats another contact’s wording Edit the email or skip the step
Suppression Conflict A stop ended a started journey Mark Reviewed to confirm
Bounce Warning A group’s bounce rate passed the warning level Mark Reviewed after checking the addresses
Task Overdue A task is one business day past due Do the task, or Mark Reviewed
Integration Failure Microsoft refused a reading or a synchronization Follow the recommended action, usually a reconnect after an administrator approves a permission
Missing Owner A task or email has no owner who can work it An approver assigns an owner

Other kinds, such as Mailbox Paused, Batch Paused for Bounces, and Approval Overdue, belong to approvers.

Escalation

Codex checks the queue every hour. A row that has waited one business day, and an urgent row at once, is escalated to the escalation user named in the settings. A business day skips weekends, United States federal holidays, and blackout dates. Clear your own rows the same day and nothing escalates.

Why a step fails

When an automated email step fails, or its send cannot be confirmed, the journey becomes Failed and an exception opens. Common causes:

  • a merge field with no value, such as a missing first name;
  • a permanent delivery failure that is not an invalid address, such as a policy rejection;
  • Microsoft 365 refusing the message;
  • tracking not being set up, which reads “The email tracker is not set up, so the email cannot carry its opt-out link.”

Fix the cause first. Retrying before the cause is fixed fails again.

The four recovery actions

The owner of the journey, an approver, or an administrator recovers a step. The actions are on the journey page’s steps list, on Sales → Exceptions, and on the Work Queue’s Exceptions tab. Each asks for confirmation.

  • Retry puts the step back on the schedule. It runs at the next opening of the prospect’s window, one step at a time. The failed attempt stays on record, and Retry never sends a message that may already have left.
  • Skip moves the journey on without the step. The journey completes if it was the last one.
  • Mark Sent and Continue is for a send that was not confirmed but is in your Sent Items. The step finishes, and the journey carries on.
  • Mark Failed is for a send that was not confirmed and is not in Sent Items. The step stays failed, and a new Step Failed row offers Retry and Skip.

Which actions you see

A step that sent nothing, because it failed before a message was written or Microsoft 365 refused it, offers Retry and Skip. Its row reads “Review the error. Choose Retry once the cause is fixed, Skip to move the journey on without this step, or end the journey from its page.”

A step whose message may have left offers Mark Sent and Continue and Mark Failed first. Its row reads “Check Sent Items for the message. If it is there, choose Mark Sent and Continue. If it is not, choose Mark Failed, and then Retry or Skip the step.” A message that is in Sent Items is also found by the next mailbox reading, which can settle the row by itself.

The rule behind both: a message that may have left is settled before the step moves on. Codex never risks sending the same email twice.

A worked example

A Step Failed row for Dana Whitfield at Bluepeak reads that the email holds {{first_name}} with no value. Dana’s record has only a last name.

  1. Open Dana’s person page, select Edit, and add the first name.
  2. Return to the row and select Retry.
  3. The step runs at the next opening of Dana’s window, and the row closes.

What you should remember

  • Sales → Exceptions has Open, Escalated, and Resolved tabs, and your rows also sit in the Work Queue.
  • A row waiting one business day escalates. Clear your own rows the same day.
  • Fix the cause of a failed step before you select Retry.
  • Retry and Skip recover a step that sent nothing.
  • After an unconfirmed send, check Sent Items, then Mark Sent and Continue or Mark Failed.

The last lesson of this module puts the whole module into a daily routine.