KB wrote:) I have therefore added a workaround to the next update which makes the microseconds optional, so that the date will work properly without them.
Thanks and all the best,
MaxG wrote:Anyone here with the same problem?
KB wrote:Great, thanks for the confirmation. Hopefully this is fixed for 3.1.2, then, as there was a time zone bug here. Let me know if you still see the issue in 3.1.2 when it's out.
All the best,