Cause (Documented platform behavior): The worker detects workflow activations that do not yield within the timeout and fails the task with the thread stack trace.
Fix status: documented_behavior
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/temporalio/sdk-python/eb642b14947bd8bcdf8816cffb6a63869803f5c6/temporalio/worker/_workflow.py (official_docs, unknown, documented_behavior): _DeadlockError.from_deadlocked_workflow builds the TMPRL1101 message and attaches the workflow thread traceback.
Search phrasings: TMPRL1101 potential deadlock detected temporal python; temporal workflow didn't yield within 2 seconds; temporal python llm call inside workflow deadlock
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Workflow task fails with a potential deadlock error and a stack trace pointing at the blocking line; task is retried.
- Context
- Product: Temporal Python SDK Component: workflow worker deadlock detection Operation: Workflow code runs a blocking synchronous call (sync HTTP/LLM request, time.sleep, heavy CPU) without awaiting Affected versions: unknown Environment: unknown Exception: _DeadlockError Packages: temporalio main at pinned SHA Trigger: Workflow code does not yield to the event loop within the deadlock timeout (2s default), e.g. a synchronous model call or long computation inside the workflow.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- [TMPRL1101] Potential deadlock detected: workflow didn't yield within {timeout} second(s).
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Temporal Python SDK] "[TMPRL1101] Potential deadlock detected: workflow didn't yield within 2 second(s)" from blocking LLM/IO call in workflow code
Recommended action: Move blocking work (model calls, file/network I/O, heavy CPU) into activities; set debug_mode only when debugging with breakpoints.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 87c709aa-809e-48e1-9cb1-b30092adc4ac
- Proposed action
- Recommended action: Move blocking work (model calls, file/network I/O, heavy CPU) into activities; set debug_mode only when debugging with breakpoints.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.