Workflow Transactional EmailWorkflow Transactional Email

Sending health

The Sending health card on the dashboard answers one question: is anything wrong with what this store sends? It looks at your senders, at the links and images in the emails you sent, and at how many events failed. When nothing needs attention it shows a single line: Everything looks good: your senders work, no broken links were found and few events failed in the last 7 days.

Otherwise it lists what it found.

Senders

Two kinds of sender problem appear here, with an Open email senders button:

  • Connected mailboxes that need to be reconnected. A Microsoft 365 or Google account whose login the provider now rejects. The dashboard banner above the card lists them by name; this line gives the count.
  • Sender alerts of the last 7 days. One line per sender, address stopped sending on date: reason, taken from the "email sender stops working" alert the app emailed you. Only the newest alert per sender is shown.

The causes and the fix for each are in Notifications and alerts; the reconnect steps are in Email senders overview.

The app checks the links and images in the emails you send and reports the ones that cannot work for anyone. The heading counts them; the table shows up to 10, newest first, and says how many more there are.

Column Meaning
Address The link or image address without its query string, marked Link or Image
Layout The layout the email was sent from or that was saved with it, as a link to its editor
Status The HTTP status the address answered with, such as 404, or Host not found when the domain does not exist
Last seen The last day this address turned up in a sent email or a saved layout
  • After every email a Flow step sends successfully, and after a test email or a resend from History, with the email exactly as it was rendered. Links that only exist in a Flow variable are covered this way.
  • When you save a layout, for the layout itself and every language it has. Addresses that are currently marked broken are re-checked right away, so a fix shows up as soon as you save.

The check never delays or fails a send; it runs afterwards.

Every http or https link and image in the email, up to 25 per email. Not checked: the app's own addresses (uploaded images, the attachment links, the unsubscribe page), any address containing unsubscribe, addresses that still contain unrendered Liquid, addresses longer than 2,000 characters, and addresses that point at private networks. Each address is checked at most once a day per store, and a store gets at most 200 checks per hour, so a large send does not turn into a flood of requests to your sites.

What counts as broken

The app asks for the address with a HEAD request and, if that is refused, a GET, waiting 5 seconds. An address is broken when it answers 404 or 410, a server error (5xx), or when its host does not exist. Everything else counts as working: a login wall (401, 403), a rate limit (429), a bot challenge, a timeout, a certificate problem or a connection reset. Those can be temporary or specific to where the check runs from, and a false alarm costs more trust than a missed one.

How long a finding stays

A broken address stays on the card for as long as it keeps appearing in sent emails or saved layouts; Last seen moves with it. It disappears when:

  • the same address answers correctly on a later check (the next send that uses it, or a layout save), or
  • you save the layout without that address in it, or
  • it has not been seen for 30 days.

Only broken addresses are stored, without their query string or fragment, so no per-customer token or order id ends up in this list.

What to do

  1. Open the layout from the Layout column and find the address. Fix the URL or replace the image, then save: the save re-checks it and the row goes away once it answers.
  2. If the address comes from a Flow variable rather than the layout, the fix is in your workflow or in your data, for example a product page or tracking link that no longer exists.
  3. A 5xx is your site or a third party having trouble. If it keeps coming back, ask the owner of that site.

Failure rate

Whenever the card has something to report, whether a sender problem, a broken link or the failure rate itself, it shows N% of events failed in the last 7 days (failed of total), with a View failed events link that opens History filtered to Failed. The Needs attention badge appears when at least 10 events ran in the last 7 days and 10% or more of them failed; that on its own is enough to replace the all-good line. Skipped marketing emails (recipients who unsubscribed) are not failures and are not counted. The failures themselves are explained in History and troubleshooting.

Unsubscribes

If you have marketing layouts, or anyone has ever unsubscribed, the card ends with the number of unsubscribes from your marketing emails in the last 30 days and a View unsubscribes link. That line is information, not a problem: an unsubscribe is the customer using the link the app put there for them. See Marketing emails and unsubscribes.