Closed BowenWang0626 closed 10 months ago
@BowenWang0626
This is intentional and by design. Its initialized there as we use the same functions for handling error and retry behavior between sync and async behaviors.
Cross thread Safeties are not required for Async Operations. That behavior is detrimental to async ops.
The lock object was initialized but never used:
While the Command_Execute, the lock object was initialized and locked: