Follow these solutions in order. Start with the least invasive and move to the more aggressive fixes.
sfdx force:mdapi:listdeployments -u <target_org>
Or with the new sf CLI:
sf deploy metadata list -o <target_org>
If an active deployment ID appears, cancel it: Follow these solutions in order
sfdx force:mdapi:cancel -i <deploymentId> -u <target_org>
If an Administrator opens the WSUS console directly on the SUP server and clicks "Synchronize Now," WSUS will start a sync. ConfigMgr will then attempt its own sync and throw SUP0108. Or with the new sf CLI: sf deploy
The orchestrator locks the service to prevent conflicting changes. If a previous update just finished, the lock might take a few seconds to release. If an active deployment ID appears, cancel it: