Skip to content

Rescheduling a failed job doesn't reexecute the underlying node instance #2171

@martinweiler

Description

@martinweiler

A process instance with a service task marked as "async" is executed and the called java method throws an exception, generating a job in ERROR state. However, rescheduling the job instance doesn't retrigger the node instance.

Current behavior

The status of the rescheduled job changes to EXECUTED but the node instance is not executed and the process instance remains in ERROR state.

Expected ### behavior
After a manual reschedule of the job in ERROR status, the job status changes to EXECUTED, the node instance is retriggered, Service Task completed correctly is shown in the application logs, and the process ends successfully in COMPLETED state.

Reproducer

https://github.com/jaimeizuz-fl-kogito/bamoe-job-reschedule-test

Steps to reproduce

  1. Clone the git repository
  2. Start the BAMOE app in dev mode: mvn -Pdevelopment clean quarkus:dev"
  3. Follow the steps in README.md contained in the cloned repo

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

📋 Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions