We confirmed the problem, and are investigating it. Of course, this will be fixed ASAP.
One workaround (and a good method in any case) is to start each macro with the command line api to run a macro non-stop.
The other workaround is to downgrade UI.Vision RPA to V5.2.3, just as @Michal_Ropka reported.