Skip to main content

Automations

Why a message was not sent

Read the run evaluation explainer in history.

Last updated 11 September 2026

Every run stores an evaluation object with the checks Cobbtree applied: automation active, quiet hours, consent, frequency cap, conditions, cutover mode and channel results.

Suppressed runs include a reason and detail string. Failed runs show delivery errors per channel.

Dual test tenants may show would_send while legacy still delivers the live message. Check your tenant cutover mode with Cobbtree support if behaviour looks duplicated or missing.

Was this helpful?

Still need help?

We are here.

Open a support ticket and we will email you a reference. We usually reply within 24-48 hours.