Next execution for cronjob does not display correctly when in other timezone

[hch-mt-dev]

Describe the bug In CronJob tab, I have a cronjob that triggers each day at 9 AM, but when looking at 10AM, in the "Next execution" column, it says the next execution is at 11 AM. My local timezone is +02:00.

The cronjob is not really triggered again. Just the displayed value in the column is incorrect.

To Reproduce Steps to reproduce the behavior:

1. Deploy a cronjob with a daily schedule on a TimeZone +02:00 for example. Choose a time so you can execute the job once, and after execution (but no more dan 02:00 after) observe the CronJobs tab.
2. Go to 'Workloads -> Cronjobs'
3. View column "Next execution"
4. You'll see something like "In 1 hour and 1 minute"
5. But you expect to see something like "In 23 hours"

Screenshots

(took this screenshot 103m after nine o'clock local time)

Environment (please complete the following information):

• Lens Version: 2025.4.92142
• OS: Windows
• Installation method (e.g. snap or AppImage in Linux):

Logs: When you run the application executable from command line you will see some logging output. Please paste them here: N/A

Kubeconfig: Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.

N/A

[koshevka]

Dear @hch-mt-dev

Thank you for reaching out to Lens Support!

Thanks for reporting a bug. We are working on your issue. Stand by for further updates.

Regards, Oleksandr from Lens