Deadline notification event is not getting triggered #3642
Assignees
Comments
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 27, 2024
…work 1) HumanTaskNodeInstance was not getting registered for job service events 2) The event published was not checking the right type of event 3) Job Service was using a different Default Unit of work manager
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 27, 2024
…work 1) HumanTaskNodeInstance was not getting registered for job service events 2) The event published was not checking the right type of event 3) Job Service was using a different Default Unit of work manager
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 27, 2024
…work 1) HumanTaskNodeInstance was not getting registered for job service events 2) The event published was not checking the right type of event 3) Job Service was using a different Default Unit of work manager
|
Kindly let me know when it will be fixed so that i can retest |
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 28, 2024
There were three issues that prevents deadlines to work 1) HumanTaskNodeInstance was not getting registered for job service events 2) The event published was not checking the right type of event 3) Job Service was using a different Default Unit of work manager
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 30, 2024
A try to avoid ramdon node disconnection affecting all client nodes
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 30, 2024
A try to avoid ramdon node disconnection affecting all client nodes
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 30, 2024
A try to avoid ramdon node disconnection affecting all client nodes
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 30, 2024
A try to avoid ramdon node disconnection affecting all client nodes
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 30, 2024
A try to avoid ramdon node disconnection affecting all client nodes
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Aug 30, 2024
This reverts commit 2ca19d2.
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Oct 10, 2024
There were three issues that prevents deadlines to work 1) HumanTaskNodeInstance was not getting registered for job service events 2) The event published was not checking the right type of event 3) Job Service was using a different Default Unit of work manager
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Oct 10, 2024
A try to avoid ramdon node disconnection affecting all client nodes
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Oct 10, 2024
This reverts commit 2ca19d2.
|
@puneetvtextellent User task functionality is getting refactor by @elguardian. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This prevents funcitonality like sending an e-mail to work
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -aorverNo response
Output of
java -versionNo 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 --versionorgradlew --version)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: