Skip to content
← Help center

Troubleshooting

Member says an automated email or text never arrived

Check a workflow’s timing, trigger, run status, and message delivery.

Club staff · 2 min read · Last reviewed October 20, 2026

Follow these steps at your club’s own website. Available screens and actions depend on your account’s role and the programs your club has enabled.

Overview

Check the workflow run and the household's message history to find out whether the workflow ran and whether the message was delivered.

An immediate step normally runs soon after the action that starts its workflow. If that handoff is missed, an automatic check normally recovers it within about seven minutes. Steps waiting for a date or delay are checked every five minutes after they become due. Busy queues, sending limits and retries can add time.

Check the message

If the member says the message came a day EARLY, check the step's timing. A step set to run on or after a date runs just after midnight on that date in your club's time zone, so a message dated the 1st should not arrive on the 31st.

A message may be delayed by the workflow schedule, blocked because the club is not live, or not delivered because the address is unconfirmed, unsubscribed, or suppressed. Text messages also require a valid number and text opt-in.

A step that says "Trying again" or "Failed"

If the email service was busy or didn't answer, an email step waits and tries again by itself: 15 minutes later, then an hour after that. Nobody gets the email twice: each try only goes to the people who haven't had it yet. While it waits, the run page shows the step as Trying again, with the emails already sent listed under it. If the third try fails too, the step shows Failed and the workflow stops there for that household. The emails listed under the step show who did get it.

A text message step is never tried again, because the people who already got the text would get it twice. If one person's number can't take texts, the others in the household are still texted.

A step marked Skipped with "its result was never recorded" started while the system was interrupted. It isn't run a second time in case it already happened, so check whether it did (a task, a tag, a note) before doing it by hand.

Do not resend a message until you know why it did not arrive. Fix the household or workflow issue, then use the supported message action. See Workflows and Why a message didn't send.