Iterable
Three silent send failures on Iterable.
Iterable workflows are powerful and composable, which means the failure surface is larger than the dashboard implies. Three silent stops the community reports most often on Iterable.
Iterable workflows are powerful and composable, which means the failure surface is larger than the dashboard implies. Three silent stops the community reports most often on Iterable.
Iterable
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.
Iterable
A workflow has a webhook node before the send. The endpoint changed authentication or moved to a new path. The webhook node retries the configured number of times then drops the user from the workflow. Downstream sends never fire for that branch.
Workflow analytics show entries dropping at the webhook step, not at the send step. The send step's own metrics look healthy because the audience that reached it is smaller but still completing. The aggregate send count drops without a per-step alarm.
The First-touch arrival window closed without a matching email.
Seed addresses entering the workflow from the same upstream event reach the send step or they do not. A silent seed inbox while the dashboard reports completions means the seed is being dropped at the webhook node.
Iterable
A campaign filters on a catalog field such as in_stock or category. A merchandising change renames the field or its values. The filter still parses, but it now matches no items, so the recommendation block returns empty, and the workflow logic that depends on a non-empty block skips the send.
Iterable does not treat an empty recommendation as a campaign failure. The send is suppressed silently per recipient. Reporting shows fewer sends but no error, and the catalog dashboard does not link the rename to the suppressed sends.
Seed the same campaign against a seed profile guaranteed to match a static catalog item. If the seed inbox goes silent while live numbers drop, the catalog filter is the cause.
Iterable
Send-time optimisation runs on a campaign. Iterable downgrades the send for recipients with insufficient engagement data, deferring them to a later window. The deferred sends sometimes never fire because the workflow ends or the user exits a segment before the window opens.
The deferral path looks like a delay, not a failure. The team waits for the late window and the late window quietly passes. There is no rollup metric that says these users were never reached.
Seed addresses set up with a fresh, low-engagement profile catch this. A working campaign sends them; a degraded one defers them indefinitely. The seed inbox going silent for the defer cohort is the signal.
Iterable
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.
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.