Hello Ankita,

There are multiple fixes in the latest version of Test Studio, regarding the Storage service and MongoDB. I would suggest you to update to the latest version 2019.2.619.0 and re-start MongoDB and Storage service, like so:
- click on the Configure button in the Scheduling section;
- in the MongoDB tab, verify that the paths are correct and click the Apply button. You should see the success message in the bottom left corner;
- go to the Storage tab and verify the configuration before clicking the Apply button. You should, again, see the success message.

If you continue to experience the same issue, please share more details about your environment and use case here, or in a support ticket, for further investigation.

Regards,
Plamen Mitrev
Progress Telerik

Hello Dylan,

Thank you for sharing detailed steps to reproduce the misbehavior.

I am sorry that you are experiencing this issue. It is caused by an unsuccessful start of the storage service. You can verify, if MongoDB is started correctly by clicking the Configure button and then clicking on the Apply button. Check the status on the bottom of the window and in case the storage service is not started successfully, please click on Apply a couple of times until you see "MongoDB is started." message. This is a timing issue with the service itself and we are working towards resolving it.

As a note to your scenario, I want to add, that all the changes are saved for your project locally. You continue to see the pop-up message "Storage service unreachable.", because Test Studio tries to send those changes to the storage service and is not  successful. When you are able to start the service and schedule new test list for remote execution, they should execute with all the changes.

Thank you for reporting this bug to us.

Regards,
Plamen Mitrev
Progress Telerik