Who this is for: Recruiters with recipients stuck in Error status in a running sequence.

Open the sequence and click the Errors tab. This shows every recipient currently blocked by an error, what the error is, and which step it occurred on. The tab only appears once at least one recipient has started the sequence.

You can also find errored recipients from the Recipients tab — filter by Error status and click any row to see the error detail panel.

For every errored recipient, four actions are available:

All four actions are also available in bulk — select multiple errored recipients with the checkboxes and apply the action across all of them at once.

Error message: "Social integration is disconnected." / "Email provider integration is disconnected." / "Text message integration is disconnected."

Root cause: The sender's integration with Social, Gmail/Outlook, or their SMS provider has expired or been revoked — typically due to a password change, a session timeout, or a provider policy update.

Fix:

Error message: "{{Candidate.FirstName}}, {{Sender.Signature}} could not be resolved."

Root cause: A personalisation token in the step content references a field that doesn't exist or is empty for this specific recipient or sender.

Fix — two options:

If the missing field affects many recipients, fix it at the sequence level: open the step editor, add fallback values to the affected tokens, save, and bulk retry from the Errors tab.

Error message: "This recipient does not have an email address."

Root cause: The recipient's profile has no email address on record.

Fix: Add a valid email address to the recipient's profile in Recruiterflow, then Retry. If you can't find their email, use Skip Step to advance them past the email step, or Stop Sequence.

Error message: "This recipient has no Social URL."

Root cause: The recipient's profile doesn't have a Social profile URL, which is required to send a connection request or Social message.

Fix: Add the recipient's Social URL to their profile in Recruiterflow, then Retry. Alternatively, Skip Step to bypass the Social step.

Error message: "Email format is invalid."

Root cause: The email address on the recipient's profile is malformed (e.g., missing @ symbol, invalid domain, extra spaces).

Fix: Correct the email address on the recipient's profile, then Retry.

Error message: "Phone number is invalid or not supported."

Root cause: The phone number on the recipient's profile is malformed, missing a country code, or is a number type not supported by your SMS provider.

Fix: Update the phone number to include the correct country code and format (e.g., +1 for US numbers), then Retry. If the number is correct but the error persists, check your Twilio or RingCentral account for country restrictions.

Error message: "Email to [address] bounced."

Root cause: The email address doesn't exist, the domain doesn't accept email, or the recipient's provider has permanently rejected delivery. Hard bounces are permanent — retrying will produce the same result.

Fix: Do not retry. Options:

Error message: "This email could not be delivered because the message size is too large."

Root cause: The email (including attachments and inline images) exceeds the size limit accepted by the recipient's email provider — typically around 25MB.

Fix: Open Edit Content for the recipient, remove or compress attachments and inline images, save, then Retry.

Error message: "The recipient's mailbox is full and cannot receive emails."

Root cause: The recipient's inbox is at storage capacity — a temporary issue on their end.

Fix: Wait 24–48 hours, then Retry. This typically resolves on its own once the recipient clears their inbox.

Error message: "Your email provider has temporarily blocked sending due to high volume."

Root cause: Your email provider (Gmail or Outlook) has flagged your sending volume as suspicious and applied a temporary block.

Fix: Wait and retry after several hours. If this recurs frequently, review your daily sending limits in Settings → Profile → Mailboxes and reduce your caps.

Error message: "This email was flagged as undeliverable during verification."

Root cause: Recruiterflow's pre-send email verification flagged this address as high-risk or invalid before attempting delivery.

Fix: Update the email address if you have a better one, then Retry. If the address is correct and you're confident it's valid, you can retry once — but a second verification failure confirms the address is problematic.

Error message: "Text message to [number] was not delivered." / "Text message could not be delivered. Please check your Twilio/RingCentral account."

Root cause: Delivery failure at the SMS provider level — possible causes include insufficient credits, number blocked by carrier, or country restrictions on your plan.

Fix:

Error message: "Social message could not be sent because your account does not have permission."

Root cause: Your Social account has lost or never granted the permissions required to send messages or connection requests via Recruiterflow. This can happen after a Social session expiry or a Social security policy change.

Fix:

Error message: "The assigned sender is no longer active or has been removed from the sender list."

Root cause: The sender assigned to this recipient has been removed from the sequence's sender list after launch, or their Recruiterflow account has been deactivated.

Fix: Go to Sequence Settings → Senders, add a replacement sender, and choose Reassign when prompted. This redistributes the affected recipients to active senders. Then Retry from the Errors tab.

Error message: "This profile is no longer available in Recruiterflow."

Root cause: The candidate or contact record was deleted from Recruiterflow after being added to the sequence.

Fix: Delete the recipient from the sequence — there is no profile to send to. No retry is possible.

Error message: "An unexpected error occurred. Please try again."

Root cause: A transient system error — usually a temporary API failure or network issue at the time of the send attempt.

Fix: Wait a few minutes, then Retry. If the error persists across multiple retry attempts, contact Recruiterflow support with the sequence name, recipient name, and the exact error message.