Hello everyone, i was doing some test using the Bank example (Java client), and for slow down the workflows i tried to put a Thread.sleep(5)… Now this is not right i guess since the worker and the server can’t communicate anymore and the WorkflowTaskFailed :
io.temporal.internal.sync.PotentialDeadlockException: Potential deadlock detected: workflow thread “workflow-method” didn’t yield control for over a second.
make sense… But, if during the sleep, i stop the worker and then i restart it, the server goes in WorkflowTaskTimedOut and will keep retry to execute the missing tasks instead of going on WorkflowTaskFailed… Is it normal or is it a bug? Can someone explain a little bit more about it? Thanks for your help