Yes, it is by design. It looks like the worker had failed or was busy. So the workflow task that was scheduled just for that worker wasn’t picked up fast enough and was rescheduled to be picked up by another worker. See the post for the details of this mechanism.
maxim
15
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Async child workflow is being called twice | 4 | 2286 | September 24, 2020 | |
| Workflow with promises is not recovering gracefully when restarting client | 29 | 1760 | February 13, 2023 | |
| WorkflowReplayer.replayWorkflowExecution throwing NonDeterministicException when reading workflow id from Workflow | 5 | 694 | May 8, 2024 | |
| Getting error in workflow when waiting for 2 hours and querying at the same time | 7 | 2564 | April 12, 2022 | |
| How to execute child workflow one at a time | 10 | 712 | July 9, 2024 |