Using 8.1.18 as depicted above, but I was also unable to reproduce this error. I also search the 2022 and 2023 change logs, and there was no mention of this.
I believe you are running into a known bug that occurs in specific timezones. Could you try testing with a timezone outside of the UTC - 6:00 to UTC + 14:00 range? If that works, then it confirms you're running into this bug.