cron scheduling either not working right or super confusing.

[cshowersPersonal]

Describe the bug
in: 4.0.1
First, when editing an existing test with a custom cron time, it doesn't retain what was already there. The user must manually set it back just to edit the script in any way

Second, the time put in via scenario setup and actually displaying on the listing are 7h different.

To Reproduce
1st problem: Just edit any existing scenario with a custom cron time and observe that the screen doesn't prepopulate the values with what was saved.

2nd problem: Schedule a time via cron and save the test. Observe the difference between what was displayed when you setup the test vs what is displayed as to when the test will actually run.

Please see attachment.

4hSPXtrrQj.mp4

[thyagram-aws]

Thanks for reporting this issue. We are currently looking into this and will update you accordingly.

[thyagram-aws]

The underlying issue appears to be that the UI for Next Runs renders timestamps in UTC, and cron schedules themselves are also interpreted in UTC. This can make it seem like the schedule is off. This will be addressed in the next release.

[thyagram-aws]

To help clarify the timestamp differences you're seeing: the “Next Runs” section displays cron-scheduled times in UTC (consistent with the previous UI), while the “Scenario Details” page shows timestamps in your local time.
Is this difference causing confusion for you as a user?
Would you prefer that the Next Runs also display times in your local timezone?

[cshowersPersonal]

Yep exactly. I was used to it displaying UTC time. I think switching between both UTC on one screen and user's timezone on another is something I didn't expect especially since nothing said it was doing that.

I'd suggest sticking with UTC time everywhere (unless you just want to make it an option) because it implies daylight savings time won't be considered and it's consistent with what's seen throughout AWS (for example cloudwatch metrics default to UTC).

Whichever way you go I'd say consistency throughout is key.