Messenger error 80006: Messenger business use case rate limit

Code 80006 is the Business Use Case (BUC) rate-limit code assigned to Messenger. Meta's rate-limiting guide maintains a table mapping each 8000x code to a product, 80001 for Pages, 80002 for Instagram, 80008 for the WhatsApp Business Management API, and 80006 for Messenger, and states that when an app reaches its BUC limit, "subsequent requests made by your app will fail and the API will respond with an error code." The documented sample for the family reads "(#80001) There have been too many calls to this Page account. Wait a bit and try again," with 80006 following the same shape for Messenger calls.

BUC limits are metered per business object, here, per Page, on Page or system-user tokens, which makes 80006 the modern, correctly-scoped signal for "this Page is over its Messenger budget": the pool computed as 200 calls x engaged users per rolling 24 hours. The accompanying X-Business-Use-Case-Usage header itemizes usage per business object ID with call_count, total_cputime, total_time percentages and, crucially, estimated_time_to_regain_access in minutes, the only place Meta tells you how long a throttle will last.

Handle it like the rest of the family (4, 17, 32, 613): stop calling, wait out the stated interval, resume slowly. Meta's best-practices list is explicit that continuing to call while throttled increases the call count and delays recovery.

{
  "error": {
    "message": "(#80001) There have been too many calls to this Page account. Wait a bit and try again. For more info, please refer to https://developers.facebook.com/docs/graph-api/overview/rate-limiting.",
    "type": "OAuthException",
    "code": 80001,
    "fbtrace_id": "AmFGcW_3hwDB7qFbl_QdebZ"
  }
}

Make X-Business-Use-Case-Usage a first-class metric: export the percentages per Page to your monitoring and alert at 80%. Size automation to each Page's actual engaged-user pool rather than a global assumption. Keep an emergency kill switch that halts non-essential Graph traffic per Page, the difference between a blip and an outage is how fast you stop calling. The BUC mechanics and every documented Messenger ceiling are tabulated in the limits reference.