-
Notifications
You must be signed in to change notification settings - Fork 213
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
Retrigger instance in error state is not working properly #3390
Labels
Comments
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Feb 28, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Feb 28, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Feb 28, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Feb 28, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Feb 28, 2024
github-project-automation
bot
moved this from 📋 Backlog
to 🎯 Done
in 🦉 KIE Podling Board
Mar 4, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 8, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 8, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 8, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 8, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 8, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 8, 2024
rgdoliveira
pushed a commit
to rgdoliveira/kogito-runtimes
that referenced
this issue
Mar 11, 2024
* [Fix apache#3390] Fixing patch * [Fix apache#3390] Fixing node not found * [Fix apache#3390] Adding IT
fjtirado
added a commit
that referenced
this issue
Mar 11, 2024
rgdoliveira
pushed a commit
to rgdoliveira/kogito-runtimes
that referenced
this issue
Mar 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Retrigger instance in error state is not working properly
Expected behavior
The workflow in
ERROR
state is retriggered successfully.Actual behavior
The workflow is not retriggered. Instead, you get the following response:
How to Reproduce?
Test workflow available at https://gist.github.com/caponetto/bae8d02d1f7aa77318f4618dd9e981bb
ERROR
stateThe response will be something like:
curl -X POST -H "Content-Type: application/json" http://localhost:8080/management/processes/wait-or-error/instances/3045d54d-35a8-4554-a656-8aebe36466d5/retrigger
The response is:
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: