Wow, thanks @vseaver! Your answer makes total sense to me. I'm guessing that using asynchronous dispatching will make my tests run faster, but I'm also concerned that it might on occasion make them break unexpectedly, so I'll just leave that unchecked for now. I checked the other one just for funsies.
I'm looking at the settings again and there are a couple more that I realize that I'm not so sure about:
Use UiaLauncher to elevate privileges for processes started by tools: Specifies whether test execution is started with elevated privileges or not.
Disable expensive attribute in tools: This setting instructs plug-ins not to evaluate computationally intensive attributes for Ranorex Spy, Recorder, and Ranorex Studio. If checked, attributes like Row.Index do not have a value for certain technologies when shown in Ranorex Spy. This improves performance is some cases.
When I check Use UiaLauncher to elevate priviledges for processes started by tools, what exactly are these tools? What exactly is happening? For example, if I run Ranorex Studio as a non-admin, but have this setting checked, does that mean that TestExecMonitor.exe will be run as an admin because TestExecMonitor is a process that is started by Ranorex, which is a tool? I checked and that doesn't seem to be the case. I'm just not really sure what this setting is doing and under what circumstances it would be advantageous/disadvantages to check it or leave it unchecked.
For the Disable expensive attribute in tools setting, I'm also not sure what these tools are that are mentioned in the setting name. Are they the same as the tools mentioned in the UiaLauncher setting? Also what would be the advantages and disadvantages of having this setting unchecked vs checked?
I occasionally notice this error occur for no reason:
The element does not support the required capability 'buttontag'.
Would unchecking the expensive attributes in tools setting prevent these errors from happening?