Thank you for clarifying what your doubts are. To describe how this feature works, I will share some notes about the Test Studio Scheduling setup and how this is designed.
The Test Studio Scheduling configuration is using the Scheduling and Storage services to control the test execution on multiple machines. The Storage service is responsible for keeping a copy of the project, which can be deployed to any execution machine, and uses the MongoDB as a storage database.
Then, once the Scheduler prepares a job for execution, the project files, which may vary depending on the tests in the test list, get deployed from the storage database to a temp folder on the selected execution machines and the test list run is then started. The temp folder is being configured in the Execution server setup.
This is the common case when the 'Get Latest from TFS' option is not enabled.
What is different when 'Get Latest from TFS' is enabled?
The only difference is that the remote TFS repository replaces the storage database. Which means that the project gets deployed from TFS to the temp folder on the selected remote machine.
So, if you have applied any changes in the project, checked these into the remote repo, and trigger a run through the Scheduling.CommandLineClient, you should see the changes within the test runs. Though, if you keep a copy of the project on the remote execution machine, this will not be affected by the test list run triggered to use the latest files from TFS.
I hope this information helps you understand what to expect from the scheduled test list runs. Of course, if you still have any concerns or doubts, please, let me know.
Thank you for your cooperation in this discussion.