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
Users calling Workflow.continueAsNew without an explicit ContinueAsNewOptions expect most workflow properties to carry over to the new run.
Actual Behavior
Right now continueAsNew is implemented in a way that assumes that most parameters are carried over by the server if not specified on the continueAsNew request. While in fact, it's the opposite. Server doesn't carry over most parameters are not carried over by the server.
Additional context
This task requires also
a careful alignment with GoSDK
documenting in Temporal API repo which parameters are carried over by the Server from the previous run.
Test server should be updated to be aligned in its behavior with the real Temporal Server.
Spikhalskiy
changed the title
Revisit continue-as-new
Revisit continue-as-new that doesn't carry over some attributes if not set explicitly
Jul 28, 2022
Spikhalskiy
changed the title
Revisit continue-as-new that doesn't carry over some attributes if not set explicitly
Revisit continue-as-new that doesn't carry over some attributes of parent run if not set explicitly
Jul 28, 2022
Expected Behavior
Users calling
Workflow.continueAsNew
without an explicitContinueAsNewOptions
expect most workflow properties to carry over to the new run.Actual Behavior
Right now
continueAsNew
is implemented in a way that assumes that most parameters are carried over by the server if not specified on the continueAsNew request. While in fact, it's the opposite. Server doesn't carry over most parameters are not carried over by the server.Additional context
This task requires also
Related:
The text was updated successfully, but these errors were encountered: