I've found a strange behavior that may exist since years...
(Numbers see attached Screenshot)
I've JOBS.001 that runs ENDED_OK (1). It's successor JOBS.002 checks the status of JOBS.001 for "ENDED_EMPTY (2) => else BLOCK (3) " . That works, JOBS.001 get's blocked within the JOBP. JOBS.002 is connected with a CALE so that it doesn't run today.
When I now press "Unblock task" (4) JOBS.001 does not get unblock, it stays in blocked status. Why is this?
Release : 21.0.4
This is working as designed.
The documentation has been updated as below
Removes the blocking condition of the task
Note: Simulates that the task has ended normally (ENDED_OK) and triggers a re-evaluation of the workflow processing.
Available for all objects.
Removes the task blocking condition and allows the task and the Workflow to continue processing.
Note: Available for blocked tasks only. It simulates that the task has ended normally (ENDED_OK) and triggers a re-evaluation of the workflow processing.