You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
Hi Jaime. Currently there are no persistence features in MicroFlow and the only way to track the flow status is to use logging. Having the ILogger.Verbosity set to LogLevel.All you can get a clue of what's going on. But tracking the data like activity constructor arguments or properties isn't currently supported. I think it's not that hard to support structured tracking in MicroFlow. For instance we can register the trackers that will be notified whenever the activity is started, finished or faulted. And notification data could include the values of every activity property. Persistence is then can be easily implemented as tracker that saves notification data into some storage.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, are there persistence features? This is, in case there is a crash in the server application, is the updated workflow data/status saved somewhere?
The text was updated successfully, but these errors were encountered: