Closed vl4deee11 closed 5 days ago
Can you try downloading the history for these failing workflows and testing with the replayer and see if the error reproduces?
https://docs.temporal.io/develop/go/testing-suite#replay
I also notice you using SetUpdateHandler
on a vey old SDK and an older Server release, Workflow Update is an experimental feature and numerous bug fixes and API changes have been made since that release so it is possible it is related to workflow update and upgrading would fix it.
@Quinn-With-Two-Ns Hello, as I wrote earlier, the replay is successful, without errors, and the only version that I can update the sdk to is 1.24.1. SetUpdateHandler
I took from the documentation here https://docs.temporal.io/develop/go/message-passing#handle-update
The latest Go SDK is v1.28.1 there are multiple bugs on fixed on the Server and SDK that could cause this behaviour your seeing. I would recommend upgrading your SDK and Server to the latest stable release.
I found one bug in sdk in version 1.24.1, now I will fix it at the level of my code, because it is very difficult to update the sdk and the temporal version in the prod, given that the latest updates did not go very smoothly
Expected Behavior
No NonDeterministicError
Actual Behavior
NonDeterministicError
I have a workflow that works great and at the end of the workflow there is a timer that does a simple thing, look at the code below:
And with this timer, everything is fine in 99.9% of cases, but sometimes a non-determinism error crashes, and the replays go normal on the same workflow on which the non-determinism error occurs
Replay works great, no problem with workflows
Stack trace:
Steps to Reproduce the Problem
Specifications
Version: