Cross-platform
Three silent send failures on your platform.
Three patterns recur across every major ESP we have looked at. They are the silent stops the community reports most often, regardless of platform. The shape is consistent: the platform keeps reporting healthy because the failure mode is a legal state, not an error.
The detection gap
What changes when a flow is instrumented.
A silent send failure follows the same six steps on every ESP. The platform handles the first two well. The next four are where the lag lives, and where the wallet card flips the timeline.
Step
Your ESP today
With Telltide instrumented
1. Trigger fires
Logged
Identical, the ESP handles this
2. Send leaves platform
Counted
Identical, the ESP handles this
3. Send fails silently
No surface
Wallet card flips amber
4. You are alerted
Not until a customer complains
Lock-screen banner within minutes
5. Triage starts
Hours later, on the next dashboard scan
From the wallet card, on the same screen
6. Fix lands
After revenue impact is visible
Before revenue impact is visible
The lag is not a tooling absence. It is the difference between a per-event log and a status surface a human checks without thinking. The wallet card is that surface.
Pattern 1 of 3
Upstream property rename silently empties the trigger audience
What it looks like
A flow or campaign filters on a custom property. An integration upstream renames the property or rewrites its values. The filter still parses but now matches almost nobody. The send counts drop.
Why detection lags
ESPs treat a small or empty audience as a legal state. The campaign keeps running. The dashboard shows the drop but does not link it to the upstream change. Discovery happens at the monthly review.
An empty audience is a legal state.
Telltide alert email, illustrative
Subject: Monitor missed: Abandoned cart
MISSED WINDOW
No email received: Abandoned cart
The Same-day recovery window closed without a matching email.
Investigate monitor →
What to instrument
Seed addresses written with the expected property values validate the filter. If seeds stop landing while older flows hold steady, the upstream property is the cause.
Pattern 2 of 3
Integration token or API key expiry breaks a send-side step
What it looks like
A flow has a step that calls out to an external system, often a CDP, a recommendation engine, or a webhook. The token expires or is rotated without the ESP being updated. The step fails. Users drop out of the flow before the send.
Why detection lags
The ESP reports the step's failures per call, not at the flow level. The flow looks healthy. The send count drops gradually as more users hit the broken step.
Failures sit per call, not at the flow level.
What to instrument
Seeds that walk the same path validate the integration end to end. If the seed reaches the send step, the integration is intact; if it does not, the token is the failure.
Pattern 3 of 3
Template merge field references a renamed or dropped attribute
What it looks like
A subject line or template body references a merge field. The underlying attribute is renamed or dropped during a data refactor. The ESP renders the field as empty or fails to send the message silently per recipient.
Why detection lags
Empty merge fields look like clean copy. Send failures per recipient lump into the broader send count without raising a flow-level alarm. Open rates dip and the team blames seasonality.
Empty merge fields look like clean copy.
What to instrument
Seed addresses with the attribute populated render the message correctly. Seeds without it show the failure. Diverging seed outcomes are the canary.
Self-audit
Ten ticks. Each one you cannot mark is exposure.
Run this against your own programme. If you finish with three or more unticked, the case for instrumenting one flow this week is the rest of this document.
-
Trigger metrics for your top three flows are reviewed monthly for rename and event-shape drift.
-
Send-skip reasons (send-time optimisation, frequency caps, send classifications, suppression hits) are aggregated to a per-flow report you maintain, since the platform does not roll them up.
-
Webhooks the flow depends on, inbound triggers and outbound callouts both, are pinged on a separate health check that fires independently of the flow.
-
Catalogue or product feed fields used in flow filters have a daily canary record that matches the filter clause and fails the build if the match returns zero.
-
Audience filters on each live flow alert if the matching profile count drops by more than a configured share week-over-week.
-
A pre-send validator catches broken template syntax and unresolved merge tags on every send, not only the compose-time linter.
-
Suppression lists driven by upstream integrations are monitored for runaway growth above a daily baseline.
-
Subscription type, consent, or preference centre changes are versioned and diffed against the previous published state before publish, so silent removals are caught.
-
Lists, segments, or upstream data feeds that power live flows have a freshness SLA and an alert if the SLA breaks.
-
Every flow critical to revenue has a seed address subscribed to it that lands within the flow's normal arrival window.
Detection Guarantee
The Detection Guarantee covers your first 90 days on Starter. If we miss a silent send failure on a monitored flow inside that window, we credit up to three months of the affected tier. One page of terms, plain English, no carve-outs.
2:12
Detail
Welcome 1 missed window
Updated
18 May 2026, 2:12 pm
Your Telltide Card. Green when every monitor is healthy. Flips amber and pushes to your lock screen the moment a flow stops sending.
Start free, instrument one flow. The wallet card unlocks on Starter, with a fourteen-day free trial when you add it. Roughly ten minutes end to end.
Cross-platform