Airship email silently stops: check the auto-suppression state first

TL;DR

The docs note you can also set suppression when registering users, and cover how suppression is removed.

Steps

1. When an address stops receiving Airship email with no errors, check its suppression_state before debugging templates or sending code. A single hard bounce or spam complaint auto-suppresses the address and Airship will quietly skip it on every future send. Look up the channel, confirm the suppression value and its cause, clear it through the documented bounce-handling flow, and only then re-test.

When to use

You are seeing this: When an address stops receiving Airship email with no errors, check its suppression_state before debugging templates or sending code. Use this skill when you run into "Airship email silently stops: check the auto-suppression state first".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Airship's official email getting-started docs describe the suppression mechanism: when Airship receives delivery feedback such as a hard bounce or a spam complaint, the address's suppressionstate is automatically updated to values like bounce, spamcomplaint, or commercialspamcomplaint. A suppressed address silently stops receiving mail with no per-send error. The docs note you can also set suppression when registering users, and cover how suppression is removed.

Verified resolution: When an address stops receiving Airship email with no errors, check its suppression_state before debugging templates or sending code. A single hard bounce or spam complaint auto-suppresses the address and Airship will quietly skip it on every future send. Look up the channel, confirm the suppression value and its cause, clear it through the documented bounce-handling flow, and only then re-test.

Source URL: https://www.airship.com/docs/developer/api-integrations/email/getting-started/