Loading...
Troubleshooting 2 min read Also available in: PT ES

Messages are not being sent — causes & fixes

The three most common causes of stuck messages in Zapini — instance not connected, daily limit and the queue — and how to fix each.

Updated on

Quick diagnosis

When a message does not go out, it usually stays in pending or failed status. The three most common causes are: instance not connected, daily limit reached and the sending queue. Let's go through each.

1. The instance is not connected

The number-one cause. Only an instance with connected status sends messages. If it is qr_ready, disconnected or offline, nothing goes out.

  • Open Instances and check the number's status.
  • If it is not connected, reconnect it (scan the QR Code again or update the Cloud API token).
  • Confirm in the global instance selector that you are on the right number.
📷 Image: instance list highlighting the connected status

2. Daily sending limit reached

To protect your number from WhatsApp blocks, Zapini limits sending to about 500 messages per day per instance, especially in bulk campaigns. Once the limit is reached, the remaining messages stay pending until the next day.

  • Check the daily sent-message counter.
  • If the limit was reached, wait for the daily reset (at midnight) or spread sending across several days.
  • For large campaigns, use scheduled messages to spread the volume.
💡 Tip: sending many messages at once increases the risk of a block. The limit and the automatic delays between messages exist precisely to protect your number.

3. The sending queue

Zapini does not fire everything at once. Messages go through a queue with small delays between each send (anti-block behavior). So it is normal for bulk messages to take a few minutes to leave, showing as pending in the meantime.

  • Wait a few minutes: the queue processes sends gradually.
  • If messages turn failed, the system automatically retries up to 3 times.
  • Messages with sent, delivered or read status already went out successfully.

Other checks

  • Active automation can block manual sending in a conversation — pause the automation to reply by hand.
  • Check that the recipient's number is correct and in international format.
  • Confirm the phone (for QR connections) is online.
💡 Tip: the status cycle is pending → sent → delivered → read. If it gets stuck in pending for a long time, review the connection and daily limit first.

Frequently asked questions

Usually the instance is not connected, or the queue is still processing with anti-block delays. Check the instance status first.
About 500 messages per day per instance, to protect the number from blocks. The counter resets at midnight.
Most likely the AI automation is active in that conversation. Pause the automation to send manual messages.
Yes. Messages with failed status are automatically retried up to 3 times by the system.

Thanks for your feedback!

Related articles