During scaledown, the Operator should recognise heuristic transactions and change the pod status to `SCALING_DOWN_RECOVERY_HEURISTICS`. However, the Operator doesn't detect the existence of heuristic transactions and the pod gets stuck in the status `SCALING_DOWN_RECOVERY_PROCESSING`.

The original issue was reported by msimka@redhat.com and the solution was provided in this upstream PR