> ## Documentation Index
> Fetch the complete documentation index at: https://openemail-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Holds and sending limits

> What stops sending, what lets it start again, and how much mail your sender lets through.

A hold keeps every message from going out until something it depends on is ready. A limit slows sending without stopping it. Neither drops a message: it waits in the queue.

## Holds

* A hold covers the whole store. More than one can apply at once, and sending starts only when every one is clear.
* Each hold lifts by itself when its cause clears. There is no override.
* Some causes need you first, such as a DNS record or a Shopify plan. Waiting alone doesn't fix those.
* A campaign going out when a hold starts carries on once it lifts, with no resume needed. Its 48-hour time limit keeps counting.
* A scheduled campaign waits up to 6 hours past its set time. After that it returns to draft and needs a new approval.

Your agent sees each hold by name in `get_status` under `holds`.

| Hold | What causes it | How it clears |
| - | - | - |
| `first_pull` | Shopify customers and order history are still coming in after install. | Lifts when the first pull finishes. Progress is on **Settings > Shopify sync**. |
| `shopify_access` | OpenEmail can't read the store: the app isn't installed, access was lost, or the store is on Shopify Basic. | Restore access, then a catch-up runs. A Basic store upgrades to Grow or higher. |
| `stale_customers` | Customer reconciliation has never succeeded or is more than an hour old. | Lifts when reconciliation catches up, so recent unsubscribes count. |
| `klaviyo` | On from install, so nobody who left your Klaviyo list is emailed again. | Lifts when an approved migration brings over your Klaviyo do-not-email list, or when a staff member confirms there's no Klaviyo account. It never comes back. |
| `domain_check` | After the domain passed once, two domain checks an hour apart failed. | Fix what **Settings > Sending domain** names, then **Check again**. Lifts when a check passes. |
| `store_erasure` | Shopify asked to erase the store's data after the app was uninstalled. | Reinstalling the app ends it. Otherwise every contact is erased 7 days after the request. |
| `restore` | The database was restored from a backup. | Lifts when sender events and a Shopify resync from the restore point both finish. See [Update and back up](https://openemail-docs.mintlify.site/run/update-and-back-up.md). |

### Not a hold, but sending still stops

* **Before the first passing domain check**, nothing goes out. `get_status` shows `blocking_domain_check: true`. See [Connect your sending domain](https://openemail-docs.mintlify.site/setup/connect-your-sending-domain.md).
* **A sender stop** is a pause, not a hold: PostShiba stopped your domain or account. Flows pick up again by themselves once PostShiba recovers. A campaign it paused needs a fresh approval to resume.
* **PostShiba account state** shows on **Settings > Sending limits**. **Waiting** means PostShiba hasn't approved your account yet. **Suspended** or **Held** means it stopped your mail. Messages stay queued either way. Contact PostShiba to find out why.

### One campaign or flow step, not the store

OpenEmail pauses a single campaign by itself when something goes wrong with it. While a campaign goes out, its bounces, blocks and complaints are counted about every 5 minutes, over all messages accepted since it started or resumed and over the latest 10,000.

| Reason on the campaign page | Trigger |
| - | - |
| **Too many complaints** | 10 or more complaints, and at least 0.1% of accepted messages |
| **Too many hard bounces** | At least 5% of accepted messages, once 1,000 are accepted |
| **Too many policy blocks** | At least 5% of accepted messages, once 1,000 are accepted |
| **The sender refused the email** | PostShiba refused the email itself, or its template failed to render |
| **The email could not be prepared** | Building the email failed 3 times for reasons outside the template |
| **The sender stopped sending** | A sender stop, as above |

Any of these needs a fresh approval to resume. In a flow, a refused email stops only that step until an approved version replaces it.

## Sending limits

Your sender sets the limits. OpenEmail follows them and sets none of its own.

* **Two limits.** Each PostShiba plan has an hourly limit and a 24-hour limit. Both are rolling: the last 60 minutes and the last 24 hours, not the clock hour or the calendar day.
* **The hourly pace.** Sending stops at 95% of the hourly limit. With a limit of 1,000 an hour, sending waits at 950, and the page shows 0 left. The 24-hour limit is used in full.
* **When room opens.** Room opens as your oldest email in the last 60 minutes leaves the window. A limit that filled at 10:50 opens at about 11:51, not 11:00. When a 24-hour limit fills, the page can't say when room opens.
* **Shared limits.** A PostShiba limit belongs to your cluster, so other mail sent on the same cluster uses it too.
* **No limits.** A sender without limits shows **No hourly or daily limit**. Then the only pace is how many messages are in flight at once.

**Settings > Sending limits** shows your sender, plan, any boost and when it ends, how much your store used in the last 60 minutes and 24 hours, and the account state. The figures are the ones sending follows: when the page says a limit is full, sending is waiting for it. Your agent reads the same figures from `get_status`.

![Settings > Sending limits: the sender and plan, the hourly and 24-hour limits, and what happens when a limit is full.](https://mintcdn.com/openemail-docs/OnJRIGCNyk9zxe6d/images/run/sending-limits.png?fit=max\&auto=format\&n=OnJRIGCNyk9zxe6d\&q=85\&s=eee9efae78436bcc00edb3011d846a03)

To raise a limit, resize your PostShiba plan or buy a capacity boost in the PostShiba dashboard. A boost raises both limits for a day. Turn on auto-boost there to start one by itself.

## Warm-up

A higher limit doesn't make a new sending domain trusted. Mailbox providers judge your domain by how people respond to its mail.

* PostShiba keeps its shared sending addresses warm, so good delivery starts with the first message. Your domain's own reputation is yours to build.
* Send the first campaigns to your most engaged contacts: recent buyers and people who opened or clicked lately.
* Cap each send with the campaign's recipient limit, and raise it while bounces and complaints stay low. When a limit cuts a list, the most engaged contacts go first.
* When a campaign is more than twice the most your sender was handed in one day over the past 30 days, its approval page warns you. You can still approve it.

Your agent follows the same plan when it builds campaigns. Moving from another provider? Keeping the same sending domain keeps its history, good or bad, so start with engaged contacts again. See [Move from Klaviyo](https://openemail-docs.mintlify.site/use/move-from-klaviyo.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.