Service Orchestration Deadlock

We're running a complex microservice architecture and I'm currently deep-diving into optimizing our internal service orchestration layer. The specific issue I'm hitting is intermittent deadlocks within our orchestration engine when certain asynchronous service calls overlap, which stalls workflows.

Here's a snippet from the logs illustrating the deadlock:

[2023-10-26T10:30:05.123Z] WARN [Orchestrator] Workflow 'OrderProcessing-XYZ' timed out after 60s. State: WAITING_FOR_SERVICE_B_RESPONSE
[2023-10-26T10:30:05.125Z] ERROR [OrchestratorEngine] Deadlock detected in orchestration context for workflow 'OrderProcessing-XYZ'. Conflicting resources: [TaskA_Mutex, TaskB_Mutex]

How have others successfully mitigated race conditions or resource contention within their service orchestration, especially in a distributed environment? Anyone faced this before?