Salesforce Marketing Cloud
Three silent send failures on Salesforce Marketing Cloud.
Marketing Cloud journeys lean on Data Extensions and Subscriber state, and most silent failures come from upstream changes to either. Three silent stops the community reports most often on Marketing Cloud.
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
Data Extension stops refreshing after an automation rename
What it looks like
A journey's entry source is a Data Extension fed by a daily Automation. Someone renames or disables the Automation. The Data Extension stops growing. The journey reports as Running with declining entries.
Why detection lags
Marketing Cloud does not link the Automation's state to the journey's health. The journey is fine; its data source is starved. The drop is visible only on the DE row count or in Automation Studio.
The journey is fine; its data source is starved.
Telltide alert email, illustrative
Subject: Monitor missed: Welcome wave 2
MISSED WINDOW
No email received: Welcome wave 2
The Day-1 send arrival window closed without a matching email.
Investigate monitor →
What to instrument
Seed records written directly into the Data Extension validate the journey downstream. If seed records flow through but live entries stop, the upstream Automation is the failure.
Pattern 2 of 3
Subscriber preference centre opts out an entire subscriber type
What it looks like
A preference page change reshapes the subscriber types or their default state. Subscribers who were opted in to a subscriber type lose that opt-in on next sync. The journey's send step suppresses for the affected subscribers.
Why detection lags
Marketing Cloud honours the preference legitimately. The journey reports as sending; the recipients silently fall out of scope. The send count drops without a journey-level signal.
Recipients silently fall out of scope.
What to instrument
Seed subscribers with explicit, isolated subscriber-type opt-ins validate the send path. If the seed stops receiving while the journey reports Running, the preference centre has shifted.
Pattern 3 of 3
Send classification suppression silently filters
What it looks like
An email's Send Classification is updated to a CAN-SPAM Commercial template that pulls a different list of suppression rules. The new suppression list is wider than the old. A meaningful slice of the audience is suppressed at send time.
Why detection lags
Send Classification changes are infrastructure work that the marketing team rarely surfaces in a campaign retro. Aggregate sends drop and engagement looks normal for the recipients who got through.
Send Classification changes rarely surface in a campaign retro.
What to instrument
Seed subscribers outside the suppression list confirm the send path. If the seed lands while live counts drop, suppression is wider than expected.
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.
Salesforce Marketing Cloud