Hi, Björn,

Thank you for following up on this topic.

This request has been tracked for several years, and at this point there is still no native solution available. While the behavior remains on our backlog, no changes have been introduced so far. I encourage you to add or reaffirm your vote on the existing public item, as customer feedback continues to play a key role in prioritization for future product updates. The product team regularly reviews these requests when planning upcoming releases.

As a workaround, the same approach described earlier is still applicable. After the daylight saving time change, you’ll need to open the scheduled job and reapply the intended execution time. This action forces the system to recalculate and store the correct Universal Time (UT), which Test Studio uses internally to determine when to start the test run.

We appreciate your continued feedback and patience. Please don’t hesitate to share additional details or use cases, as they help us better understand the impact of this limitation.

Regards,
Stoyan
Progress Telerik

Hi Sunil,

You are correct that this feature request was created a few years ago and there is no solution implemented. Please add you vote in the public item to increase its importance for the upcoming releases and the product management team will evaluate it.

In the meantime, you can apply the workaround that was described in the initial message by Lori. Essentially, you need to edit the scheduled job and re-apply the setting with the new time, after daylight savings. That will update the Universal Time (UT) that Test Studio uses to measure the time and start the test run.

Thank you for your feedback and understanding.

Regards,
Plamen Mitrev
Progress Telerik