Stop the "float" on recurring runs

[cshowersPersonal]

Describe the bug

1. The scheduled time for a recurring daily run floats . Meaning over time it changes slightly each run.

2. Also if you kick off the daily scheduled run, the next scheduled time is changed.

To Reproduce

1. Create a daily recurring test.
   Let it run for a few days.
   Watch the time change over time.

2. Create a daily recurring test
   Run it manually
   Observe the next scheduled time has changed.

Expected behavior
The saved scheduled time should remain. I cannot find any value in how it operates today.

The original scheduled time in the screenshot was 6AM . This is a minor example, I typically adjust it every time I change the script. I've seen it deviate as much as 7 minutes in the past.

[kamyarz-aws]

Has it ever been more than 15 minutes?

[cshowersPersonal]

For #1 not that I've noticed. Like I said I update tests regularly and when I do I fix the start time.

For #2 it's really more of an annoying problem. If you have a nightly run that you want to run outside of the scheduled time, the new scheduled time gets updated to the time you're running off-schedule. Which then requires you to edit the test and fix the time.

Bottom line it doesn't make sense that scheduled time changes to last executed time after the test is saved.

[cshowersPersonal]

Should also mention that we run automated tests and performance tests through the night after our US personnel stop working but before our poland personnel start working. It's only about a 5 hour window and our timings matter because they can step on each other and skew results.

[kamyarz-aws]

For the first Issue, Can you confirm if step function was triggered on time?

For the second one, this doesnt strike me as a bug as you just mentioned. We can create a feature request to add like a exception times so your original time wont change but you can kick a non-scheduled test.

[cshowersPersonal]

For first question, sorry I do not understand. Can you please explain? For second question: The SCHEDULED start time is being replaced by LAST RUN TIME. Seems like a bug, but if that's a feature then ya it would be really nice if the SCHEDULED time stays the SCHEDULED time unless the test is edited and the scheduled time is changed.

[kamyarz-aws]

For the second one, That is the expected behaviour. It is designed to set the time automatically only if you start a test now and set the test to rerun daily/weekly on the same time you started the test. Now if you set a time, but start at some other time, the second time takes precedence. That is why I meant when I say it is not a bug. Now we can work out a feature so through GUI maybe you select a checkbox to not override the time, or something like that. For the first one I am looking into it and How it can be enhanced. Some time change is relatively okay because every day we create a new a rule, and that rule have some time shifts. I cant generate a time shift more than 30 seconds on my end. But as I said I try to make it more consistant.

[kamyarz-aws]

@cshowersPersonal This will be addressed in our next release

[kamyarz-aws]

@cshowersPersonal The latest release is addressing the issue.