Why a send was held or refused

Mujaz checks every send before it goes out. An issue can be held for a quick review, moved to just after midnight by the daily limit, or refused for a specific reason. The message you see points to the cause and the fix.

Last updated:

New accounts warm up

In the first 24 hours one send can reach at most 500 people; in the first 7 days at most 5,000. You'll see “New accounts warm up gradually…”. Send to a smaller list, or ask support to verify your account; verified accounts have no warm-up.

Held for a quick review

You'll see “This send needs a quick review before it goes out…” and an “Awaiting approval” badge on the issue. This happens when:

  • The send is much larger than any before: over 2,000 people and more than 3× your biggest send.
  • The sender name looks like a well-known brand.
  • The content reads like a bank, order or account notice.
  • Links go through shorteners, raw IP addresses or other services' trackers.

Mujaz reviews it within a few hours and emails you the result. If it's refused, the badge reads “Not approved”; hover it to see the note. Full, direct links help, and a verified sending domain skips the content and link checks.

Refused or paused

  • Dangerous link: if Google Safe Browsing flags a link in the issue, the send is refused. Remove the link and send again.
  • Sending paused: “Your account is under review and sending is paused…” or “This workspace has been suspended…”. Only support can lift it. It can also happen automatically if many of the first emails bounce or are reported as spam.

Nobody to send to

  • “… has no subscribers yet…”, “… no active subscribers…” or “Nobody on … matches the audience filter…”: add people, pick another list in “Audience Segment”, or loosen the filters.
  • “You must select an audience segment”: choose a list in the Audience tab → “Audience Segment”.
  • “You must add at least one content block…”: the issue is empty.
  • “Please fix the errors / Some required fields are missing information.”: usually the Featured Image is missing, or the title or subject.

Monthly and daily limits

  • “Email limit exceeded. Remaining: X, Required: Y”: the send doesn't fit in your monthly allowance, so the whole send fails. Change your plan or wait for the 1st of the month.
  • If a send would pass the workspace's daily limit before anything went out, it's moved to just after midnight (UTC) and goes out then. Its card in Scheduled says why. If it's larger than a whole day's limit, contact support.
  • “Daily send cap reached”: contact support.

Failed sends

A failed issue shows in Drafts with a “Failed” badge and the reason. Fix the problem and press “Send again”; people who already got it are skipped.

Common questions

How long does a review take?

Usually a few hours. The result comes by email.

Will people get it twice if I send again after a failure?

No. “Send again” skips everyone who already received it.

How do I avoid a review?

Use full, direct links instead of shorteners, and send from your own verified domain if your plan has it.

  • Send an issue now or schedule it

    In the Review step, choose “Send immediately” or “Schedule for later”, then press the send button. You can cancel a schedule from the Scheduled tab as long as sending hasn't started.

  • Common error messages

    What Mujaz's most common error messages mean, and what to do about each. Many still appear in English even in the Arabic interface.

  • Plan usage and limits

    Each plan has a monthly allowance of emails and AI uses, plus a limit on subscribers and team seats. Email and AI allowances reset on the 1st of each month, and on each paid renewal.

  • How to stay out of spam

    Send only to people who asked for your newsletter, use full direct links, send to engaged readers, check the “Spam Score Checker” tips before sending, and send from your verified domain if you can. Mujaz handles the rest: an unsubscribe link in every email, no more mail to bounced or complaining addresses, and link checks before sending.