-
Notifications
You must be signed in to change notification settings - Fork 209
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
Workflow finalizer / abort hook #3674
Comments
If the DELETE call that abort a workflow would throw an exception, then by configuring a global, or by state,
|
After discussing this issue further, I think we can automatically execute compesating states if the workflow is aborted by calling delete endpoint. |
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Sep 30, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Sep 30, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Sep 30, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Sep 30, 2024
fjtirado
added a commit
that referenced
this issue
Oct 2, 2024
rgdoliveira
pushed a commit
to rgdoliveira/kogito-runtimes
that referenced
this issue
Oct 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The way we currently to it is by updating the state via a graphQL mutation request sent to the DI so there is no known way to me to execute a state that is executed before aborting the workflow.
This would be nice to be able to set a finalizer / abort hook that is always executed when canceling the workflow: if the workflow already started some external execution or made some changes, it would be nice to be able to revert those.
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: