Hello, We were trying out temporal schedules, but we noticed that all our schedules stopped running intermittently. We are seeing the workflows created for temporal-sys-per-ns-tq queue are failed due to this error : “Potential deadlock detected: workflow goroutine “root” didn’t yield for over a se…

[Screenshot 2024-03-04 at 4.09.57 PM] Attaching 1 more screenshot for failure log and call stack

[image] Go SDK Troubleshooting Developer Corner Go Troubleshooting What to do when you encounter a bug When an unexpected error/bug is found in a workflow or activity, there are many ways to fix it. The most important thing you can do is reliably replicate th…

@maxim , thanks for the link , but here the issue we faced was with the internal workflow used by temporal for scheduler, how should we go about debugging that ?

Can you check if your worker is running too hot on CPU? If CPU start to throttle your worker role, you would see this error.

No that doesn’t seem to be the case , our temporal worker cpu was between 10 to 30 % only

Facing issues with temporal schedule

Community Support

maxim March 4, 2024, 7:26pm 3

Topic		Replies	Views
Workflow task worker error: failure executing SCHEDULED->WORKFLOW_TASK_STARTED Community Support	11	3820	January 14, 2021
When starting worker, get the Potential Deadlock error, can anyone suggest? Community Support	4	2944	March 30, 2021
Issues with temporal schedule feature Community Support	0	242	May 15, 2024
PotentialDeadlockException, when does this happen? Community Support java-sdk	7	928	September 28, 2024
Potential deadlock detected. Workflow thread and didn't yield control for over a second Community Support	3	863	January 9, 2024

Facing issues with temporal schedule

Related topics