Small and medium business | Business Central, N...

The time is not valid in the current time zone

(2) Share

Report

Posted on by Ajay Babu Chikati

Our customer who is in US experiencing an error that is stating “The time is not valid in the current time zone. For example, when the clock is adjusted forward, any time in the period that is skipped is invalid.” while keying in General Journals.

is this something to do with daylight savings time?

Customer subscribed to BC SaaS and current version got updated is 19.4.
Please se the error screenshot below. Kindly advise.

2BB5BDAA_2D00_AA82_2D00_43E9_2D00_A2BF_2D00_683078F594EF.jpeg

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

IB-29041624-0 1,177 Moderator on at

Like (0)

Report
Copy link

Link copied!

This has probably something to do with DST.

I would suggest you raise a support ticket with Microsoft around this to get their explanation for it.

And if you do so, please share the result here.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 100,278 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi, you can check the settings of My Setting again, this appears to be an issue with the regional or language settings. And you can debug it in your environment first.

But if there was no problem last week and there is a problem this week, it's probably a DTS problem. As far as I know the DST was adjusted just in time from this week.

Hope this info will help.

Thanks

ZHU

Was this reply helpful? Yes No
Joyce NAMC 10 on at

Like (0)

Report
Copy link

Link copied!

We are experiencing the same error with our email logging Job Queue. It began only after the time change.

I have checked my admin settings and everything looks correct.

Can someone please explain to my what DTS is? Thank you. Joyce

Was this reply helpful? Yes No
Ajay Jain 229 on at

Like (0)

Report
Copy link

Link copied!

I am getting the same error, any solution?

Was this reply helpful? Yes No
NW-01041524-0 2 on at

Like (0)

Report
Copy link

Link copied!

Same error - originally seen on 26.x, we've since updated to 27.5. I've cleared the job queue log, and even tried setting up entirely new job queues as well, same results... The only workaround we've found is to set the time zone of the user running the job queue entries to Marquesas Islands (UTC -9:30), which of course triggers the jobs to run 3.5 hour late.

Error text:
Job finished executing.
Status: Error
Error: The time '3/8/2026 2:25:09 AM' is not valid in the current time zone. For example, when the clock is adjusted forward, any time in the period that is skipped is invalid.

Was this reply helpful? Yes No