When a message cannot go out, a red reason and a Retry link appear under the bubble in the chat. The panel does not hide the reason, because some failures need waiting, some need a setting changed, and some need nothing at all. This guide opens up the reasons one by one.
You may be facing one of these three situations:
The message is red and a reason is written under it
Retry does not help
There is no message box at all
💡 Read the reason first. The panel does not print the same text for every failure; it tells you which gate stopped the message, and the right step depends on that.
The 24-hour window is closed
What you see: "The 24-hour messaging window is closed", or a longer line under the chat saying exactly when the window closed.
Why: More than 24 hours have passed since the person's last message. Free-form text cannot be sent.
What to do:
On WhatsApp, use the template picker that stands in place of the message box; see Sending a WhatsApp template.
On Instagram, look at the badge in the contact panel. If it says Human agent: until …, you can write directly.
If neither applies, wait for the person to write again.
What you see: "The account's access is invalid; reconnect the channel", or "This account's connection has a problem; reconnect it under Settings › Connection to reply."
Why: The access Meta granted has become invalid (it expired, the account password changed, the permission was withdrawn). When the panel gets this error it marks the connection as faulty, and no message can be sent from that account.
What to do:
Open the Settings › Connection page.
Sign in again with the same account.
Return to the inbox and try the message again.
Until the connection is fixed, both sending and receiving stop.
Meta's rate limit and network errors
What you see: "Meta's sending limit was reached; try again shortly", or "Could not reach Meta".
Why: The first is a short-lived rate limit on Meta's side; the second is a temporary network or server problem.
What to do:
Wait a few minutes.
Press the Retry link under the bubble.
If it keeps happening, slow your sending down; an automation may be pushing out a lot of messages at once.
These two are temporary, so retrying really can help.
The content was refused
When the channel objects to the message itself, the cause is either the file's format or the length of the text.
A file was refused
What you see: an unsupported file or file too large warning.
Why: The format is not on that channel's list, or the size limit was exceeded. Limits differ per channel and per type.
Convert the file to an accepted format (JPEG or PNG for images, MP4 for video, PDF for documents).
If it is a size problem, shrink the image or lower the video resolution.
This failure is permanent too: retrying with the same file will not work.
The text is too long
Why: Instagram measures the text limit in bytes rather than characters, and accented letters take 2 while emoji take 4. After placeholders are filled in, the text may have crossed the limit.
What to do: Shorten the text or split it in two. Cutting emoji frees up more room than you would expect. If you are using a saved reply, think about the filled-in version: a template that looks short can cross the limit with a long customer name.
There is no message box at all
This is a gate rather than a failure. It has three possible causes:
You do not have permission. Someone in the Viewer role cannot write replies.
The window is closed. A template picker or a yellow warning line stands in its place.
The connection is not active. The yellow line tells you to reconnect.
The line on screen says which one it is.
If the problem continues
Close the conversation and open it again; the error may be left over from an old screen.
Reload the page.
Try writing to the same person from the Instagram or WhatsApp app on a phone. If it fails there too, the problem is on Meta's side.
Renew the connection.
Send a short message in a different conversation. If sending works elsewhere, the problem is specific to that person rather than the whole account — usually the window or a restriction on that contact.
A failed message stays in the chat and is not removed on its own. Rather than leaving an unwanted attempt sitting there, read the reason and pick the right route; that is the fastest way to avoid the same failure twice.
Known limits
Retrying a failed automation message does not give it the human agent period; it goes through the 24-hour rule.
Retrying an automation message that had buttons does not resend the buttons; only the plain text goes out again.
Private replies to comments follow their own rules: once per comment and within 7 days of the comment. For a live broadcast comment, nothing can be sent once the broadcast has ended.
A conversation outside your scope cannot be messaged by any route; even with the link in hand, the server refuses.
If you have worked through every step and the problem persists, contact our Support team.