Replyz / Guides / Why the email never arrived
Why didn't the email my AI agent was waiting for arrive?
The agent filled in a sign-up form, called wait, and got a timeout. Before you blame the service, check these in order. The first four are about the address and the account; the last ones are about your filters. Use it only where a service's terms allow automated sign-ups.
Short answer. Check that the address is exactly the one issued, that the account has not expired, that the message is under 10 MiB and the monthly cap is not reached, then list the inbox without filters. A wait that times out is a normal result: it only means nothing matched in time.
1. Is the address exactly the one Replyz issued?
A Replyz address ends in a six-character suffix, for example guide-demo-neat-oyster-6lz2rx@youreplyz.com. A mistyped or shortened address has no inbox and the mail is refused. Copy the address from the signup answer or from status.
2. Has the account expired?
A sandbox account lasts 24 hours. Once expires_at has passed it works as expired at once and new mail is refused. Check it:
npx -y @replyz/cli status
status: sandbox
expires_at: 2026-11-16T21:51:48.228Z
limits: {"inboxes":1,"receive_per_month":1000,"send_scope":"none"}
usage: {"inboxes":1,"received_this_month":0}
That is real output from a production test account (9 November 2026). A human who claims the account before it expires gets the claimed limits and the account no longer expires; after expiry the claim link no longer works. See how claiming works.
3. Is the message too large, or the account over a cap?
- Messages over 10 MiB are refused.
- A sandbox account takes up to 1,000 received messages a month; a claimed account up to 5,000.
- One sender (or all unauthenticated mail together) can use at most 20 % of the monthly cap. Above that, that sender's mail is refused while other senders' mail still arrives.
The agent is not notified when mail is refused. status shows the usage.
4. What does the sender see when Replyz refuses a message?
One generic text for every reason, so a sender cannot learn the state of an account. The sending server shows:
555 5.7.1 mailbox unavailable.
When we sent a message from a Gmail account to an address that did not exist on 6 November 2026, it bounced in about 3 seconds with that text. If the service you signed up at reports a bounce or "address rejected", this is the cause to look at: unknown or mistyped address, deleted inbox, expired account, size, or a cap. If the failure is on Replyz's side, the sender instead gets a temporary error and tries again later.
5. Do your wait filters match?
fromis a case-insensitive glob (*,?) that must match the whole sender address, for example*@accounts.example.com. A service that sends from a different domain than the one you guessed will not match.subjectis a case-insensitive substring.- All filters must match. Drop them to test.
sincehides mail received before it. The default is 10 minutes back, which finds a code that arrived just before the call; do not setsinceto the exact moment of your call.
6. Did it arrive, and was it already returned?
List the inbox without filters:
npx -y @replyz/cli messages ls --limit 10
If the message is there, the problem was a filter or exclude_returned (which skips messages that wait or a read already returned). If it is not, the service did not send it yet, sent it elsewhere, or Replyz refused it. See how to wait for an email in code.
Still stuck?
Write to hello@replyz.io with the inbox address and the time you triggered the email.
Frequently asked questions
Why didn't the email my agent was waiting for arrive?
Check, in order: the address is exactly the one issued (it ends in a six-character suffix); the account is not expired (a sandbox lasts 24 hours); the message is under 10 MiB; the account is under its monthly receive cap; and your wait filters (from, subject, since) really match the mail. A wait that times out is a normal result, not a failure.
What does the sender see when Replyz refuses a message?
One generic text for every reason: the sending server sees 555 5.7.1 mailbox unavailable. The sender cannot tell whether the address is unknown, deleted, expired or over a cap, on purpose. The agent is not notified of refused mail.
How do I see whether an email arrived at all?
List the inbox's messages without filters (replyz messages ls, or GET /v1/inboxes/{id}/messages) and check the account status. If it is not listed, the sending service did not deliver it, or Replyz refused it.
Why does wait time out when the mail is there?
Usually a filter. The from filter is a glob that must match the whole sender address and the subject filter is a substring; both are case-insensitive. A since time later than the mail's received_at also hides it, so use the default 10-minute look-back.
How long does a sandbox account receive mail?
24 hours from signup, with up to 1,000 received messages a month. After that the account works as expired and refuses new mail. A human who claims the account gets higher limits.