Current checks on the termination controller may return a wrong state of the transaction store in case of network errors during recovery scan. In particular, "orphans" may not be detected.

JBTM-3017 will add a new check that we should use in order to ensure that all resources have been contacted during recovery scan. Without JBTM-3017, the only way to do the same check seems to be parsing the application logs.

We should check if we always respect the following condition:
"... note that recovery scans can occur before applications are deployed so it is the callers responsibility to only rely upon the result of the operation after all deployments have completed. We do this with EAP on OpenShift by running the readinessProbe.sh which guarantees the deployment is up and has registered all its required resources (ie the operation will therefore be guaranteed to attempt contact with all possible resources)."

We can think to add a equivalent call to actuator.