Messenger error 613: Message tag abuse warning

Code 613 with subcode 2018338 wears a rate-limit code, but read the message: it is a policy warning, and an unusually explicit one. "You are engaging in behavior that may be considered bothersome or abusive by users. You must significantly decrease the rate at which you are sending messages using message tags to this person. Further misuse of API features may result in messaging restrictions being placed on your Page." Meta is telling you, per recipient, that your tagged-message volume toward that person has crossed the line, and naming the consequence if it continues.

Message tags exist to carry narrow, non-promotional exceptions across the 24-hour window, in 2026 that effectively means HUMAN_AGENT (and the customer-feedback template flow), since the update tags were retired in April. Tags are therefore the platform's most policed surface: each tagged send bypasses the user-consent structure of the window, so frequency toward a single person is treated as a proxy for abuse. Unlike the volume throttles (2534040, 4), waiting does not reset the concern; the pattern itself must change.

Take the escalation path seriously: this warning is a documented precursor to Page-level messaging restrictions, the territory of 368. The correct response is not to spread sends across the day but to ask why one person is receiving many tagged messages at all, almost always a bug (a loop re-sending a notification) or a flow misdesign (status updates that should be batched or opt-in).

{
  "error": {
    "message": "(#613) Warning! You are engaging in behavior that may be considered bothersome or abusive by users.",
    "type": "OAuthException",
    "code": 613,
    "error_subcode": 2018338,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Enforce tag discipline structurally: a per-recipient budget on tagged sends, idempotency on every notification, and code review for any new use of MESSAGE_TAG. Tags are a compliance surface, not a delivery channel. The tag rules and their 2026 reductions are tabulated in the Messenger limits reference, and the enforcement ladder is described with error 368.