Node.js + MySQL: How to prevent the "Double-Shift" Timezone offset on Datetime fields?

[EinfachChris]

Hi everyone,

I’m struggling with a timezone synchronization issue in a Node.js project that is breaking my real-time countdown timer. I’ve spent hours trying to find a clean way to sync Server time, DB time, and Browser time, but I keep hitting a "Double-Shift" offset.

The Setup:

• Server: Node.js (Wappler)

• DB: MySQL 8 (Table uses DATETIME columns)

• Frontend: App Connect dmx-datetime calculating secondsUntil() a DB timestamp.

The Problem:

When I save a timestamp from a Server Action using NOW or NOW_UTC, it looks correct in the database (e.g., 2026-04-23 22:15:00).

However, when I fetch this value via a Server Connect query, Node.js seems to "assume" the database time is local. It then applies a conversion, and the JSON output arrives at the browser as a UTC ISO string with a -2 hour offset (e.g., 2026-04-23T20:15:00.000Z).

Because the browser is actually at 22:15 local time, the App Connect timer immediately drops to 0 because it thinks the expiration time was 2 hours ago.

Current JSON Output: "question_expires_at": "2026-04-23T20:18:23.000Z" (even though the DB says 22:18)

What I've tried:

1. Using NOW_UTC in all server-side calculations.

2. Manually adding offsets like .dateAdd('hours', 2) (which feels like a "dirty fix" and will break during DST changes).

3. Using TIMESTAMP instead of DATETIME in MySQL.

My Question:

What is the "Wappler-way" to ensure that a DATETIME value from MySQL is delivered to the frontend 1:1 without Node.js shifting the hours based on perceived server/local timezones?

Is there a specific setting in the Database Connection or a Moment.js/Node environment variable (TZ) that I should be using to keep everything strictly in sync for a countdown timer?

Thanks in advance for your help!

[Teodor]

Can you clarify what you want to do? Do you want to output the database stored date/time to the user exactly as it is stored in the db? Or do you want to convert it to users' local time?

Check the 3 examples in the following documentation, maybe you want to do what is explained there:
https://docs.wappler.io/t/date-and-time-settings-for-nodejs/46102/

[EinfachChris]

Hi Teodor,

I'm working on a quiz tool.

Here I need a countdown that's synchronized between the moderator, the players, and the database.

[Teodor]

Please check the link i posted and see the examples shown there, choose the one that fits your needs.

[EinfachChris]

Unfortunately, that doesn't help me either.

I need a timer that counts down from the variable "timer_limit" and records this in the database.

I want to use this to verify the user's buzzer interaction.

I've been going around in circles with this AI for two days now and I'm not getting anywhere.

How would you solve something like this?

[Teodor]

@EinfachChris

I need a timer that counts down from the variable "timer_limit" and records this in the database.

I am not really sure i understand what you are doing. Your initial post explains something about displaying date from the database on the page without converting it to local time, then here you are referring to countdown timer.
Can you please start from the beginning and explain what the issue exactly is?

[EinfachChris]

I'm working on an interactive quiz tool.

I want to set a time limit during, which users can press the buzzer. When the time expires, the buzzer will be disabled.

Therefore, I need a timer that synchronizes via socket between the moderator's browser, the player's screen, and the display (screen, scoreboard).

[Teodor]

Ok, so what problems do you have with the implementation of this and how is this related to the intil post in this topic, about displaying dates from the database on the page?

[EinfachChris]

My problem was the different time zones on the online server, local server, and user browser, which prevented me from synchronizing the timer. I've already tried setting my local server to UTC, but honestly, that's too complicated for me.

[ben]

Try this by going to Workflows > Globals > db and click the three dots at the top as shown here:

In the dropdown, choose Open in Code Editor

In the Code Window add "dateStrings": true inside the options object as in:

{
  "connection": {
    "server": "localhost",
    "user": "root",
    "password": "",
    "database": "mydb",
    "options": {
      "dateStrings": true
    }
  }
}

Hopefully this will fix the problem.

As a note to the Wappler Team, it would be great if this were available in the UI - that is if this works.

[EinfachChris]

hi Ben,

This it how it looks like for me.

Solved sync issues

Bypassing Timezone Issues for Live Timers (Integer-based Sync)

The Problem: Syncing real-time timers via UTC timestamps frequently leads to drifts, lag, and complex timezone offsets between server and client—unacceptable for live quiz events.

The Solution:

1. Ditch Datetime: We stopped comparing end-times (datetime) in the database.

2. Master Clock: The Moderator’s browser acts as the pulse. It calculates the remaining time locally using dmx-datetime.

3. Integer Sync: The "seconds remaining" are sent as a simple Integer to the database and broadcasted via Socket payload.

4. Passive Clients: Participant browsers receive the raw number and display it directly without any local time calculations.

Result: 100% synchronization across all devices with zero timezone logic. By shifting the calculation to the Moderator’s frontend and using a simple integer for the sync, we eliminated drift and significantly reduced server overhead.

Thank you for your help!!