You may need at least a basic error handling and logging implemented to figure out what goes wrong.
Try adding an On block error action and encapsulate your entire flow with it. Then add rules for it to call a separate sub-flow (you will need to create it first) and have that sub-flow use Get last error to get the details of the error and Write text to file or Display message to either log the error to a file or display it in a pop-up dialog. This way you will be able to capture the error and figure out what's wrong.
My best guess here is that the debugger is designed to run slower than actual runtime on purpose, so you can debug issues. And it might be that you've built your flow in a way that assumes that is the normal speed. But when it runs in actual runtime (what you call the "view mode"), it runs much faster and some parts of your SAP application may simply not keep up with the speed at which your flow performs its actions. But in order to verify this (and to resolve it), you will first need to figure out what it is exactly by implementing my suggestion above.
-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.
I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.
