Brief description
Under certain circumstances, Conduits do not seem to "scale down" as described in the documentation, keeping shards above the maximum shard count "alive" instead.
How to reproduce
Create a Conduit with 2 Shards
Connect 2 WebSocket Transports to the Shards
Disconnect WebSocket with Shard ID 0 (unsure at the time of writing if required)
Scale down Conduit to 1 Shard
Observe unchanged Conduit Status
Expected behavior
Shard with ID 1 should have been disabled/deleted and either a "status" of "deleted", "scaled_down" or similar should be set or not be present in the list of shards anymore.
The "extra" shards will still "change status" if the transport assigned changes state (which conceptually will be never for a webhook, but more likely on a websocket)
Brief description Under certain circumstances, Conduits do not seem to "scale down" as described in the documentation, keeping shards above the maximum shard count "alive" instead.
How to reproduce
Expected behavior Shard with ID 1 should have been disabled/deleted and either a "status" of "deleted", "scaled_down" or similar should be set or not be present in the list of shards anymore.
Additional context or questions Refer to Discussion on Discord in #eventsub-help