-
Notifications
You must be signed in to change notification settings - Fork 627
Timers in persisted machines #311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
yeah, that's a different issue but I created #321 for it. Tried it and definitely a bug. |
Thanks for the update |
@davidtepel you could actually check if fix(1.2.3 snapshots) for #321 helped with this issue as I made some fixes to stop triggering when machine is stopped. |
Actually we had to find another solution for the timers becuse of this bug and also, a requirement in which the timeout of the timer should be dynamic. i.e, change the periodic timer timout on the fly without creating a new state machine (in order to change retry mechanism in the same state machine). |
This obviously is a very tricky. Lets say that there is a timer which fires and may take machine to some other state. Nothing will happen if machine is not running(as it is hibernated into storage). Should think some ways to do this.
The text was updated successfully, but these errors were encountered: