-
Notifications
You must be signed in to change notification settings - Fork 18
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
Do not set workflow completion until after all coroutines have settled in the task #481
Open
5 of 9 tasks
Labels
enhancement
New feature or request
Comments
This was referenced May 17, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 11, 2024
This was referenced Jul 11, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 15, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 15, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 15, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 15, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 15, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 15, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 17, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 17, 2024
dandavison
added a commit
to dandavison/temporalio-sdk-core
that referenced
this issue
Jul 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem
Today in core-based SDKs, we set workflow completion immediately upon workflow return and discard anything else that may happen on the same task. In Go/Java, we let the coroutines all complete even if they make commands and then set workflow completion after that. We should do the same in core-based SDKs.
In order to do this in a backwards-compatible way, we will need to leverage SDK flags. And in order to not have to put this flag on every workflow henceforth, SDKs will need to determine whether there are post-completion commands after the workflow returns.
An approach (EDIT: this is what was decided) (EDIT2: we decided not to go with this):
SDKs can choose one of the two options:
Option 1:
Option 2:
Another approach (EDIT: this was decided against) (EDIT 2: we decided to do this)
Describe the solution you'd like
Decision
We're going with the first approach above. And core doesn't need to do anything, it already allows flags.
Per-SDK Tickets
The text was updated successfully, but these errors were encountered: