Yeah, you would need to provide more details as to when or why it is getting a timeout error. Like for example, if you are minimizing or closing the RDP window then that will be the issue which @Florent_Salendres mentions a potential solution for above.
Another culprit I have seen is in Windows Server where the Start Screen is the first screen that comes up when you login, where the UI can not see the desktop. There was a registry fix to disable the Start Screen on logon for Windows Server 2012 but in Windows Server 2012 R2 I believe it was suppressed by default.
There are some other settings in Windows Server that can cause issues as well, like the Desktop Experience needs to be enabled if I remember right.
If it times out while you are watching it, then in that case, it’s most likely a selector or timing issue.
Launch Workflow Interactive was a method to solve for interactions that are impacted by resolution or color depth, and could also be a way to simulate unattended by turning on the console use. However, Orchestrator v18 supposedly addresses this with the option to set resolution settings for each robot. If the workflow is being run as attended then it really doesn’t matter because it will use the settings that you are logged in RDP with.