What
The self-hosted-runner gateway process now tracks how many client requests are currently open compared to how many it is able to forward upstream at the same time. When the number of open requests exceeds the configured (or default) outbound concurrency limit, it logs a rate-limited warning.
The warning suggests either adding more replicas or raising BUN_CONFIG_MAX_HTTP_REQUESTS, along with the replica's memory limit, to allow more concurrent outbound requests.
Why
This helps operators running a self-hosted gateway notice and diagnose a bottleneck before it causes request failures or timeouts, and points them directly at the two knobs (replica count and BUN_CONFIG_MAX_HTTP_REQUESTS) that can relieve it.