The customer is experiencing an issue when attempting to assign 1000 lead records, receiving an error message indicating a failure to connect to the server due to a timeout request.

The underlying cause was identified as a batch call from the UI that triggers 1000 individual assign operations, which takes over 10 minutes, leading to a timeout of the W3wp thread. Although the backend continues to process the request, the UI displays an error. From the UI team's perspective, this is currently the system's design. The root cause can be explained as follows: if the Lead entity owners have overridden the Assign command with their own custom implementation, while all other entities use the Assign All API, this discrepancy causes issues specifically for the Lead entity owner.

Therefore, it is expected that "assign all" should work fine and not throw any errors to ensure seamless business operation