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
Current behavior is that Forge will remember the CurrentTreeNode of the Subroutine and visit that node on failover/retry.
What if the user would like to start from the RootTreeNode on retry?
I could see either behavior making sense, so we should add a property flag in SubroutineInput to determine the desired behavior.
Probably would need to delete all the state from subroutine session before retrying. I don't want to parse through the data though, so perhaps just starting a brand new subroutine SessionId would suffice.
The text was updated successfully, but these errors were encountered:
The text was updated successfully, but these errors were encountered: