> ## Documentation Index
> Fetch the complete documentation index at: https://help.pipelime.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Resting days, sending windows and deferrals

> Why a healthy mailbox sits out a whole day, and every other reason a send waits instead of going out.

export const Screenshot = ({id, alt, caption, frame = 'browser', url, marks = [], lang = 'en', workspace = 'northwind-outbound'}) => {
  const src = `/images/screenshots/${lang}/${id}.png`;
  const chrome = url ? `app.pipelime.ai/${workspace}${url}` : 'app.pipelime.ai';
  return <figure className={`pl-shot pl-shot--${frame} not-prose`}>
      <div className="pl-shot__frame">
        {frame !== 'bare' && <div className="pl-shot__bar">
            <span className="pl-shot__dots">
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
            </span>
            <span className="pl-shot__url">{chrome}</span>
          </div>}
        <div className="pl-shot__media">
          <img src={src} alt={alt} loading="lazy" />
          {marks.map(mark => <span key={mark.n} className="pl-shot__mark" style={{
    left: `${mark.x}%`,
    top: `${mark.y}%`
  }} aria-hidden="true">
              {mark.n}
            </span>)}
        </div>
      </div>
      {caption && <figcaption className="pl-shot__caption">{caption}</figcaption>}
    </figure>;
};

Outreach from a mailbox only goes out inside the weekly hours set for it, and on top of that every mailbox draws a small chance each day of sitting the whole day out. Neither is a fault and neither is a status: a send that either one blocks waits and is tried again, and a rest day never holds back a reply to a lead.

<div className="pl-availability">
  <div className="pl-availability__row">
    <div className="pl-availability__label">Where</div>
    <div className="pl-availability__value"><span className="pl-path">Integrations<span className="pl-path__sep">→</span>Integrations<span className="pl-path__sep">→</span>Email Accounts</span></div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Your role needs</div>
    <div className="pl-availability__value">Read access to Email Accounts <code>read-senders</code>. Admin, Member and Viewer have it by default.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">To create or change</div>
    <div className="pl-availability__value"><code>create-senders</code> to add one, <code>update-senders</code> to change one, on top of the permission above.</div>
  </div>

  <div className="pl-availability__note">If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.</div>
</div>

## How it behaves

### A healthy mailbox occasionally takes the whole day off

Every mailbox is rolled independently for a chance of resting on any given calendar date: about 5%, drawn fresh per mailbox per date. The roll looks only at the mailbox's own id and today's date, so there is nothing to configure: a rest day can't be scheduled for a particular day, moved, or turned off from the app. It also means every part of the product that touches the mailbox today (the campaign engine, warm-up traffic, workflow blocks, and the screens that report on it) resolves the same answer for the whole day, without checking in with each other.

The point of the roll is to break up a pattern spam filters watch for: a mailbox that never misses a single day, at exactly the same volume, doesn't look like it's run by a person. Occasionally sitting a day out is what a human's mailbox does.

On the list, a resting mailbox carries a **Resting today** chip beside its name. Resting is not a status and it does not touch the status column, so an otherwise healthy mailbox still reads **Active** there. That pairing is the thing that looks like a bug until you know it's deliberate. The mailbox's own page carries the fuller explanation as a banner.

<Screenshot id="email-accounts/resting-days-and-schedule--resting-chip" url="/senders" alt="The Email Accounts list: one row carries a coffee-cup Resting today chip beside the mailbox name, and an Active chip in the status column at the right" caption="A representative example: which mailbox rests is a fresh roll on every calendar date, so this pairing is captured against a simulated response." />

<Screenshot id="email-accounts/resting-days-and-schedule--resting-banner" frame="bare" alt="A mailbox's own settings page with an amber banner headed This mailbox is resting today, explaining that new outreach and follow-ups resume tomorrow while replies to leads still go out today" caption="A representative example: same reason as the list chip, so this banner is captured against a simulated response." />

By default, a rest day only holds back campaign email. Warm-up traffic isn't part of what it protects, so a mailbox can show zero new outreach for the day while still quietly exchanging warm-up mail inside its usual hours.

### A reply is never held by a rest day

A rest day only ever withholds messages the mailbox is starting: new outreach and follow-ups. A lead who has replied to you gets answered regardless. The job that looks for something to send checks for a pending reply before it ever checks whether the mailbox is resting, so the two decisions never interact. The same split holds inside a workflow: a **Send Reply** block never asks whether its mailbox is on a rest day, and a **Send Email** or **Send Follow-up** block always does.

### Whether a new mailbox has a sending window depends on how you added it

A mailbox sends only inside the hours set for it on its [settings page](/en/email-accounts/sender-settings), and it does not always arrive with any.

Filling in the mailbox form yourself, or taking the **Import senders** route, starts you on a Monday-to-Friday schedule split into a morning block and an afternoon block. Those blocks are read in the time zone of the browser that set them and stored in UTC. The availability grid converts them back on the way out, so a colleague in another time zone opens the same mailbox and reads different clock times than you typed. A mailbox on managed infrastructure gets the same two weekday blocks, but they are written in UTC rather than in anyone's local time, so unless you are on UTC the grid shows them shifted.

A mailbox added through **Connect your email** gets no schedule at all, and it sends nothing until you set one. Its status column reads **No Schedule** instead of **Active**, and its name cell carries a muted calendar icon that opens nothing, in place of the schedule button described below. It never shows the moon either, so don't read a quiet row as an off-hours one.

### Outside its hours, a row shows a moon

Outside its schedule, a mailbox's row carries a muted moon icon. Hovering it says when the mailbox will be available again, in UTC and in your own local time.

<Screenshot id="email-accounts/resting-days-and-schedule--off-hours" url="/senders" alt="A mailbox row with a muted moon icon and its tooltip open, saying the sender is currently unavailable due to schedule configuration and naming when it will be available next, in UTC and in local time" caption="The tooltip gives both times, so you don't have to convert UTC yourself to know when it picks back up." />

The calendar button on the same row opens a popover onto today's actual send times: a clock face and a list of the specific moments, not just the blocks you set, that the mailbox plans to use today. The list is in your own local time, and hovering a point on the clock face gives that time and its UTC equivalent.

<Note>
  This popover's own title and time labels stay in English on every language setting. The one exception is the rest-day message it shows in place of a schedule, which is the same translated banner as above.
</Note>

When a mailbox is resting, its row never also shows the moon, even outside its own schedule window. The two would otherwise look like two separate problems sitting on the same row, when there's really only the one.

### Campaign email is rechecked every minute

The process that looks for campaign work runs once a minute and re-evaluates every mailbox from scratch. It picks a mailbox up only when the mailbox is **Active**, it has a running campaign to work on, the current minute falls inside one of the send moments generated for it today, it is under its daily limit, and enough time has passed since its last email. Nothing schedules a retry for later: the pass a minute from now simply asks again.

Replies go through the same door. That minute-level filter runs before the job can tell a waiting reply from new outreach, so a reply from a mailbox outside its hours waits for the next in-window minute like everything else. What a reply skips is the rest day, and only the rest day.

### In a workflow, a blocked send waits on its own timer

Workflow blocks don't share the campaign engine's every-minute pass. A **Send Email** or **Send Follow-up** block held up by the mailbox's hours, its daily limit or the gap since its last email rechecks itself after a randomized 45 to 90 minutes, so a fleet of waiting blocks doesn't all retry on the same clock. A block held up by a rest day skips that short retry and waits for the mailbox's next morning instead, at a randomized time between roughly 07:00 and 09:00 UTC, rather than polling through a day whose answer isn't going to change.

Neither wait is unlimited. Each keeps its own count and gives up at a ceiling, and an enrollment that hits one ends with the status **Completed**, not **Failed**. [How workflow sends are scheduled](/en/workflows/how-sends-are-scheduled) lists the ceilings and what each one looks like on the enrollment.

A **Send Reply** block skips all of this. It asks only that the mailbox is **Active** and not archived, so it writes its message regardless of the mailbox's hours or its rest day.

### Other reasons a send doesn't go out

A rest day and the schedule window are only two of several reasons a healthy-looking mailbox doesn't send. A brand-new mailbox can hold all campaign email back for a separate reason of its own, and its daily limit keeps changing for a while after that. A lead in another country can hold up outreach to them alone, on a public holiday there, without touching anyone else's mail. And a mailbox that's paused, in error, or otherwise stuck can look much like a resting one at a glance. The Related cards below cover each of those.

## Limits

|                                                         |                                                                                       |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Chance a mailbox rests on any date                      | About 5%, rolled fresh per mailbox per calendar date                                  |
| What a rest day holds back                              | New outreach and follow-ups only; replies and warm-up traffic still send              |
| Default schedule, mailbox form or **Import senders**    | Weekdays only, a morning block and an afternoon block, read in your own time zone     |
| Default schedule, managed infrastructure                | The same two weekday blocks, written in UTC                                           |
| Default schedule, **Connect your email**                | None; the mailbox reads **No Schedule** until you set one                             |
| Campaign engine recheck                                 | Every minute, automatically, for every mailbox                                        |
| Workflow block recheck (hours, daily limit or send gap) | A randomized 45 to 90 minutes, up to a ceiling                                        |
| Workflow block resume after a rest day                  | The next day, at a randomized time between about 07:00 and 09:00 UTC, up to a ceiling |
| A workflow's **Send Reply** block                       | Exempt from both the schedule window and the rest day                                 |

## Related

<CardGroup cols={2}>
  <Card title="Sender settings: limits, schedule and signature" icon="sliders-horizontal" href="/en/email-accounts/sender-settings">
    Every field on the mailbox form, including the weekly schedule this page assumes you've set.
  </Card>

  <Card title="National holidays and out-of-office pauses" icon="calendar-off" href="/en/leads/holidays-and-out-of-office">
    The other calendar-driven pause: one lead's own country, never your mailbox's clock.
  </Card>

  <Card title="Reading the sending capacity timeline" icon="trending-up" href="/en/email-accounts/capacity-timeline">
    Why a brand-new mailbox sends nothing at all at first, and how its limit changes after that.
  </Card>

  <Card title="This mailbox is resting today" icon="triangle-alert" href="/en/troubleshooting/sender-shows-active-but-nothing-delivers">
    Every reason a mailbox can show Active and still deliver nothing, not just this one.
  </Card>
</CardGroup>