PM-173535-19-202747
An absence of service was identified in an environment with a high volume of devices associated with the same software distribution. When multiple devices reported the progress of packets at almost the same time, each report updated the overall execution log again. This frequency of writes to the same log resulted in lock contention and exhaustion of available database processes in Azure SQL, resulting in the worker limit error (10928).
The process is adjusted so that the overall run record is not updated in each package progress report. Starting with this release, the update is performed only when the overall execution status changes, and only the status and date of the log update are modified. This reduces the load on the database in high-concurrency scenarios, without altering the final result of the distributions.