Defect #1303
Updated by Alena Peterová over 5 years ago
Version 8.1.7
If there are multiple asynchronous provisioning operations nearby, sometimes one of them stays in provisioning queue as "Not executed" and it's never executed. This operation also blocks all future provisioning operations. It must be retried manually, no automatic process handles it.
Situation:
* The system "IDB export" has asynchronous provisioning.
* The task ProvisioningQueueTaskExecutor is scheduled every 10 seconds.
* I change the value of an EAV and then change it back quickly
* Two provisioning operations are created after EAV save of the same identity
* One of the provisioning is executed correctly, the second stays in the queue as "Not executed - Account has some unfinished provisioning tasks in queue"
The problem is probably some race condition - ProvisioningQueueTaskExecutor runs just when the provisioning operations are created. They are in the same batch, but the executor processes only the first operation. Please see the screenshots and note the same time in ProvisioningQueueTaskExecutor and provisioning operations.
In our (slow) environment, this race condition happens cca in 1 out of 3 attempts. It's quite