Meta messaging windows and limits

Three separate checks

Messaging windows, API request rates, and DMFLOW's monthly allowance are separate conditions. Available monthly capacity cannot reopen an old conversation, and a higher plan cannot override Meta restrictions.

A comment's first private reply

An eligible comment can receive one private reply within seven days of its actual creation. This is separate from the age of the post and the webhook delivery time. That first reply does not authorize further automated DMs by itself. The person must respond; opening a website link is not an incoming message. Meta has a separate restriction for Instagram Live replies during the broadcast; this guide does not promise DMFLOW support for Live automations.

Ordinary DMs and later steps

For an ordinary DM, DMFLOW checks the 24-hour window since the person's latest incoming message. It checks when queueing and again immediately before sending. An expired message is not sent. A fresh response from the person can open a new window; the app does not manufacture recipient responses or use a human-agent exception to authorize automation.

When the API slows down

Meta can limit requests by API, account, or app. We do not promise one universal sending rate for every account. After HTTP 429 or a recognized rate-limit response, DMFLOW delays an eligible attempt and progressively increases the interval, up to one hour. Messaging windows and the monthly allowance still apply. An ambiguously confirmed send is not automatically repeated.

An exhausted monthly allowance is a separate reason to wait. The studio shows the actual limit; proposed public pricing does not change it. Duplicating rules or repeatedly enabling them does not bypass these restrictions.

Primary documentation

Meta: Private Replies explains the first reply and follow-up window. Meta: Instagram Platform overview explains request limits. DMFLOW also applies its own conservative queue checks and duplicate protection.