Local Agent doesn't trigger automatically from CMD and how to solve it?

Issue:

When the user schedules a test run and starts a local agent. The agent keeps freezing after response with status 200 without running the execution

The user has to trigger the execution manually by clicking or pressing enter on the CMD

 

 

Reason

The issue ended up being a new feature of the windows 10 console. Under the default config, whenever you click on a command window in windows 10, it immediately pauses the application process when it attempts to write to the console.

When this happens, the command window has gone into "selection" mode because QuickEditMode has been disabled (unchecked)

 

Solution

Enable the QuickEdit Mode:

1. Right-click on the top left bar > Select Default

 

 

2. Select and check on QuickEdit Mode → OK

 

3. Restart CMD again and start running the execution