In Concurrency packs, you can use the Disconnect from user feature to "remove" all users who are currently occupying the concurrency pack. For example, if 20 concurrencies in a concurrency pack is being used, this number will change to zero after the concurrency pack is disconnected from the users.
How do I fix the issue of abnormal concurrency usage?
If you find that a user is occupying a concurrency for a long time in a test, you can use the disconnection feature to remove the user.
During technical integration, the SDK callback can be used to check whether a user is inactive for a long time. You can customize the idleThreshold parameter to set the threshold for user inactivity, so that the DestroySession API can be called to release the concurrency after the callback is received.
Do not use Disconnected and DestroySession at the same time, Just choose one of them. Otherwise, the concurrency cleanup time will be extended.
If the frontend user directly closes the page to close the connection to CAR, as DestroySession is not called, the CAR concurrency will wait 90 seconds for the user to reconnect. We recommend you maintain a heartbeat connection between the business backend and the client to check the user status and close the connection.
