I have a set of tests that are scheduled to run weekly, one per day. For example, Test 1 runs on Monday, Test 2 runs of Tuesday, etc. Last week, the Monday test did not run. When I investigated, I found that all the tests had planned dates for the next week. I changed them back to last weeks dates and they ran at the proper time. After they ran, I checked and made sure that the planned dates had been updated to this week. This morning (Tuesday), todays test did not run. I checked the planned dates and they are set for next week. The last executed dates correspond with last week, but all the planned dates are now set to next week. What is causing the planned dates to change to the next week? Note that ALL of the planned dates have changed to next week, so theyre not being changed by the running the tests. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/2085.aspxthreadId=2085Karl Tinsley (Karl.Tinsley@peci.com) I have a set of tests that are scheduled to run weekly, one per day. For example, Test 1 runs on Monday, Test 2 runs of Tuesday, etc. Last week, the Monday test did not run. When I investigated, I found that all the tests had planned dates for the next week. I changed them back to last weeks dates and they ran at the proper time. After they ran, I checked and made sure that the planned dates had been updated to this week. This morning (Tuesday), todays test did not run. I checked the planned dates and they are set for next week. The last executed dates correspond with last week, but all the planned dates are now set to next week. What is causing the planned dates to change to the next week? Note that ALL of the planned dates have changed to next week, so theyre not being changed by the running the tests. Tue, 03 Sep 2019 13:24:19 -04002019-09-10T09:56:19-04:00/Support/Forum/spirateam/issues-questions/2085.aspxmessageId=3655Karl Tinsley (Karl.Tinsley@peci.com) We have discovered the cause for this issue. There were two people logged into the machine where the test was running, and each had an instance of RemoteLaunch running. Each instance was starting the test, but one was failing because there was no desktop (its a GUI based test). We have stopped the second instance and expect the problem to be resolved now. Wed, 04 Sep 2019 13:53:03 -04002019-09-04T13:53:03-04:00/Support/Forum/spirateam/issues-questions/2085.aspx#reply3655messageId=3657David J (adam.sandman+support@inflectra.com) Thanks for posting the answer. Regards David Tue, 10 Sep 2019 09:56:19 -04002019-09-10T09:56:19-04:00/Support/Forum/spirateam/issues-questions/2085.aspx#reply3657