# Why aren't people receiving my message?

Start here to figure out why people aren’t receiving messages at the right time.

Note that people who are [unsubscribed from topics or from all messages](/journeys/subscriptions-overview/) can still trigger a campaign; they just won’t receive messages from that campaign.

## Check your message’s settings[](#check-your-messages-settings)

Select the message block to get started.

[![The message settings panel shows the message name, sending behavior, subscription preference, message limit, and action conditions.](https://docs.customer.io/images/message-block-settings.png)](#e37300310f0b739b4e31e95e85a50a63-lightbox)

### Check your message’s sending behavior[](#check-your-messages-sending-behavior)

Select *Settings* to check your message’s sending behavior.

By default, messages are set to queue as [drafts](/journeys/queue-draft/) in your campaigns. [Update them to send automatically](/journeys/queue-draft/#change-sending-behavior) then [send any drafts](/journeys/queue-draft/#send-drafts) manually to ensure all of your campaign’s audience receives the messages.

### Check the subscription preference and message limit[](#check-the-subscription-preference-and-message-limit)

Select *Settings* to check your message’s subscription preferences and message limit settings. By default, they inherit your campaign’s settings, but it’s possible to override them.

*   Is the person subscribed to receive this message?
*   Has the person reached the message limit? If so, they won’t receive this message. This message would be marked as “Undeliverable”.

If the message inherits the campaign-level settings, click the campaign title and view *Messages* to see which subscription preference was assigned and what message limit is in place.

### Check whether the message is a holdout test[](#check-whether-the-message-is-a-holdout-test)

Select *Experiment*. If “Make this message a holdout test” is selected, then people won’t receive the message.

### Check message conditions[](#check-message-conditions)

You can add [action conditions](/journeys/action-conditions/) to a message to limit who receives it. If a person doesn’t meet the action conditions, they won’t receive the message and will move onto the next item in your workflow. The person’s journey for the campaign will show they skipped the message.

[![image.png](https://docs.customer.io/images/skipped-message.png)](#32ad29607b87f04dd0b81034d2954c9b-lightbox)

## Check if the message failed to send[](#check-if-the-message-failed-to-send)

If the message has a status of “Failed”, then you might have a liquid error. Check the message content to see if any errors are present.

## Check if the email address is suppressed[](#check-if-the-email-address-is-suppressed)

[A suppressed email](/journeys/esp-suppression/) won’t receive emails from Customer.io. If you manage email deliveries through Customer.io, check your suppression list in [*\> Workspace Settings > Email > Suppression List*](https://fly.customer.io/workspaces/last/settings/actions/email/suppression_list).