# Communications and automation troubleshooting

> Diagnose email, messaging, calls, Inbox, workflows, sequences, forms, and published assets without duplicating work.

Canonical: https://help.spacebrain.ai/troubleshooting/communications-and-automations/

## Email or message was not received

Check sender account health, recipient validity, consent and suppression, send-from identity, workflow execution, outbox or thread, provider delivery status, recipient spam or filtering, and quiet-hour or registration controls. “Sent” may mean accepted for delivery rather than delivered.

## Inbox is missing a conversation

Clear channel, owner, status, search, and date filters. Confirm the provider connection and whether the provider has the event. Force a supported **Sync now** only once, then wait for processing.

## Call did not connect

Confirm number assignment, country capability, contact format, consent and calling window, campaign state, agent state, usage, provider status, and destination carrier behavior. A completed call record can still represent voicemail, no answer, or provider disposition rather than a successful conversation.

## Workflow did not start

Verify the workflow is enabled, trigger event occurred after enablement, conditions match, record belongs to the active workspace, and another automation did not alter the field first. Imports and merges can behave differently from manual edits.

## Workflow failed partway

Open the specific execution and first failed node. Inspect input and provider state. Determine which earlier nodes completed before retrying. Correct the cause and use the safest supported resume or retry path.

## Sequence step did not send

Check enrollment, current step, schedule and timezone, stop condition, reply state, suppression, sender account, missing variable, and workspace entitlement. Confirm whether a live edit applies to existing enrollments.

## Form submitted but no lead appeared

Open the form’s **Responses**. If the response exists, inspect mapping, duplicate behavior, integrations, and workflow executions. If it does not, test the live published URL, validation, browser console or blockers, and the success redirect.

## Published content is stale

Confirm you edited the published asset rather than a copy, save and publish state, target domain, CDN or browser cache, DNS, and whether the provider is still processing media. Test in a private browser and compare the exact URL.

<Callout type="warn" title="Check the destination before retrying">
  A timeout or stale UI can occur after the provider completed the action. Verify the mailbox, phone log, social network, calendar, CRM, payment provider, or live page first.
</Callout>