Back

[SOLVED] Invalid datetime on $createdAt & $updatedAt attributes

  • 0
  • Databases
Chris
25 Sep, 2023, 12:51

Am getting difficult configuring my local timezone when creating documents. Appwrite does not pick the correct time zone from system.

The documets saved are 1hour behind my localtime.

TL;DR
Title: Issue with Incorrect Timezone for $createdAt and $updatedAt attributes [SOLVED] Messages: The user was having difficulty with the $createdAt and $updatedAt attributes being 1 hour behind their local time. It was suggested to use UTC for all server-side operations to maintain consistency in a distributed cluster. The user mentioned Appwrite not accurately picking the system's timezone when creating documents. The problem was eventually resolved.
darShan
25 Sep, 2023, 15:38

Appwrite uses UTC.

Chris
25 Sep, 2023, 18:52

Thanks @darShan

Drake
25 Sep, 2023, 19:10

FYI, in general, it's a good idea to use UTC for everything server-side. this makes things standards in cases where you may have a distributed cluster for your backend

Chris
25 Sep, 2023, 19:13

@Steven This is well understood.

Drake
25 Sep, 2023, 20:42

[SOLVED] Invalid datetime on $createdAt & $updatedAt attributes

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more