Skip to main content
Start at the top: the first steps stop every email, the later ones stop one campaign, one flow or one person. Your agent can run the same checks: ask it to “read get_status and tell me why email isn’t arriving.”
1

Is sending held?

  • The symptom: nothing goes out at all.
  • Open Home. Sending is held lists each blocker and who acts on it.
  • Work through A send is held to clear it. Messages already queued go out once every hold lifts.
Checkpoint: Home reads Sending is on.
2

Is PostShiba accepting your mail?

  • Open Settings > Sending limits and read the account state.
  • Waiting: PostShiba hasn’t approved your account yet. Until it does, it delivers only to your PostShiba team’s own addresses and its live inbox addresses. Finish its approval steps in the PostShiba dashboard.
  • Suspended or Held: PostShiba stopped your mail. Messages stay queued. Contact PostShiba to find out why.
Checkpoint: the account state reads Approved.
3

Is a limit full?

  • The symptom: email goes out, but slowly or in bursts.
  • On the same page, see how much of the hourly and 24-hour limits your store used. A full limit keeps messages queued until room opens, and the page says when, where it can.
  • Nothing is lost. To send faster, raise the limit with PostShiba. See Holds and sending limits.
Checkpoint: room left under both limits, or a time when room opens.
4

Is the campaign or flow actually sending?

  • A campaign sends only after approval. On Campaigns, Draft means it still needs one, Scheduled means it waits for its set time, and Paused shows why on its page. A campaign OpenEmail paused needs a fresh approval to resume. See Campaigns.
  • A flow sends only while Live. On its page, a step marked Stopped sends nothing: the sender refused its email. Ask your agent to fix the email and request approval again. See Flows.
  • An abandoned checkout starts the flow only when the shopper gave an email address and placed no order within 10 minutes of their last change. Any order ends the run.
Checkpoint: the campaign reads Going out or Sent, or the flow reads Live with no stopped step.
5

Was this person left out?

  • The symptom: most people got it, one didn’t.
  • Open Contacts, search the full email address, and open the contact. Check that the badge reads Subscribed, and that Do-not-email entries shows no active entry.
  • A campaign also leaves out contacts over the recipient limit, and can skip anyone emailed recently. Its page counts who was left out, by reason.
  • You can’t lift an unsubscribe, a hard bounce or a complaint. Only an entry added by hand can be lifted, with a person’s approval. See Unsubscribes and the do-not-email list.
Checkpoint: the contact is subscribed with no active do-not-email entry.
6

Accepted, but not in the inbox

  • Accepted means PostShiba took the message at hand-off. It doesn’t mean it reached the inbox.
  • Ask the person to check spam and promotions folders.
  • Open Settings > Sending domain. Each problem names the record at fault, the value expected and who fixes it. Fix it and choose Check again.
  • A new sending domain needs warm-up: small sends to engaged contacts first. See Holds and sending limits.
Checkpoint: Every setting passed the last check.
7

Test emails only

  • Test emails go only to active test addresses, under Settings > Test addresses. You can have five.
  • While PostShiba hasn’t approved your account, a test to any address outside your PostShiba team comes back as not approved yet. That’s PostShiba’s restriction, not a broken email.
  • Test emails skip the consent check but still respect the do-not-email list.
Checkpoint: the test arrives at an active test address.
Still stuck? Ask your agent to read get_status and the campaign or flow, and to quote any reason it finds. It sees the same facts the admin shows.
Last modified on November 5, 2026