-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Some batch operations (like cancel process instance) fail in case the process instance is already completed at the point in time the operation runs. This can create many failed batch jobs which are hard to get rid of. However, this operation does not need to fail, the process instance is already completed so there is no use to fail the operation: the user's desired end state is already reached.
Note while working on this:
- decide whether the same idempotent behavior could/should easily be implemented for other operations (delete process instance from history for example)
- decide to in addition work also on a general solution to deleting batch operations with many failed batch jobs, see
CAM-9551
This is the controller panel for Smart Panels app
[CAM-9553] Idempotency of cancel process instance batch operation
Description |
Original:
Some batch operations (like cancel process instance) fail in case the process instance is already completed at the point in time the operation runs. This can create many failed batch jobs which are hard to get rid of. However, this operation does not need to fail, the process instance is already completed so there is no use to fail the operation: the user's desired end state is already reached.
Note while working on this: decide to in addition work also on a general solution to deleting batch operations with many failed batch jobs, see |
New:
Some batch operations (like cancel process instance) fail in case the process instance is already completed at the point in time the operation runs. This can create many failed batch jobs which are hard to get rid of. However, this operation does not need to fail, the process instance is already completed so there is no use to fail the operation: the user's desired end state is already reached.
Note while working on this: * decide whether the same idempotent behavior could/should easily be implemented for other operations * decide to in addition work also on a general solution to deleting batch operations with many failed batch jobs, see |
Link | New: This issue is related to SUPPORT-4563 [ SUPPORT-4563 ] |
Description |
Original:
Some batch operations (like cancel process instance) fail in case the process instance is already completed at the point in time the operation runs. This can create many failed batch jobs which are hard to get rid of. However, this operation does not need to fail, the process instance is already completed so there is no use to fail the operation: the user's desired end state is already reached.
Note while working on this: * decide whether the same idempotent behavior could/should easily be implemented for other operations * decide to in addition work also on a general solution to deleting batch operations with many failed batch jobs, see |
New:
Some batch operations (like cancel process instance) fail in case the process instance is already completed at the point in time the operation runs. This can create many failed batch jobs which are hard to get rid of. However, this operation does not need to fail, the process instance is already completed so there is no use to fail the operation: the user's desired end state is already reached.
Note while working on this: * decide whether the same idempotent behavior could/should easily be implemented for other operations (delete process instance from history for example) * decide to in addition work also on a general solution to deleting batch operations with many failed batch jobs, see |
Link | New: This issue is depended on by SUPPORT-5251 [ SUPPORT-5251 ] |
Workflow | Original: camunda BPM [ 53962 ] | New: Backup_camunda BPM [ 56599 ] |