Discord.js REST Queue: Intermittent Connection Pool Exhaustion Diagnosis

Diagnosing Intermittent Queue Exhaustion in Discord.js

The goal is to determine when the internal REST request queue in discord.js v14 reaches its internal limit and causes sporadic latency spikes or request failures under high traffic.

Constraints include the undocumented queue size threshold (default 500 pending requests), the lack of a public API to expose queue metrics, and the fact that exceeding this limit may silently back‑pressure the caller instead of rejecting requests outright.

Given these uncertainties, the key question is how to reliably detect and differentiate true connection pool exhaustion from normal rate‑limit back‑pressure.

Specific Questions

• Which internal properties or debug logs can be used to monitor the RESTManager’s queue size and processing rate in a production‑ready way?
• Is there a supported configuration option to adjust the maximum queue length or to enable automatic flushing when the limit is reached?
• How does Discord’s own rate‑limit enforcement interact with the discord.js queue, and can it trigger the observed intermittent failures?