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
The issue I am experiencing is that a Kogito process seems to be stuck in an 'active' status. Upon investigating the relevant Kafka topic, it appears that the event changing the process status to 'completed' and setting the 'endDate' is being published before the event signaling the process start. This anomaly in the process event sequence might be causing the process to remain stuck in the 'active' state.
The Kogito version used is 1.33, and the application is Spring-based
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of uname -a or ver
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 or gradlew --version)
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
If the event that is supposed to end the process is consumed by Kafka before the event that is supposed to start the process, there is no way to fix this other than changing the sequence of events (that might be a problem, but not a kogito problem)
This will be a Kogito issue if that event is published by the starting process and the starting process has not registered to the event yet, but Im not sure this is the case you are experiencing.
I think we need confirmation of the exact scenario
Describe the bug
The issue I am experiencing is that a Kogito process seems to be stuck in an 'active' status. Upon investigating the relevant Kafka topic, it appears that the event changing the process status to 'completed' and setting the 'endDate' is being published before the event signaling the process start. This anomaly in the process event sequence might be causing the process to remain stuck in the 'active' state.
The Kogito version used is 1.33, and the application is Spring-based
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
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: