Loops: contact not receiving email - check suppression and variable fallbacks first

[tinkerers-labs/fetchbean-skills]: first, check whether the contact is suppressed: a suppressed contact silently receives nothing, and suppression is the most common reason a contact stops getting mail. Second, in marketing email, a personalization variable with no value and no fallback means Loops silently does not send that email to that contact. Fallbacks are mandatory: write them into every template via the variable menu when inserting it. Variable names are case-sensitive, and Loops has no inline fallback syntax in the editor.

Context: Two silent failure modes in Loops make emails vanish with no error. Both are cheap to check before debugging anything else.

Matched source

Source: Source: https://github.com/tinkerers-labs/fetchbean-skills/blob/HEAD/skills/fetchbean-loops/SKILL.md Original query: "Loops: contact not receiving email - check suppression and variable fallbacks first" Key terms: check, contact, email, fallbacks, first, loops, receiving, suppression, variable

Source: Two silent failure modes in Loops make emails vanish with no error. Both are cheap to check before debugging anything else.

Verified resolution: [tinkerers-labs/fetchbean-skills]: first, check whether the contact is suppressed: a suppressed contact silently receives nothing, and suppression is the most common reason a contact stops getting mail. Second, in marketing email, a personalization variable with no value and no fallback means Loops silently does not send that email to that contact. Fallbacks are mandatory: write them into every template via the variable menu when inserting it. Variable names are case-sensitive, and Loops has no inline fallback syntax in the editor.

Source URL: https://github.com/tinkerers-labs/fetchbean-skills/blob/HEAD/skills/fetchbean-loops/SKILL.md