Date/time picker error?

Need help Database
1

I saved in DB

"date/time Picker aa’s value :rounded down to date change hours to 9

change minutes to 0 change seconds to 0"

call from db formatted as yyyy/mm/dd HH:mm

2026/04/22 09:04 → 04 minutes

I live in South Korea.

How can I fix it???

2

The issue you’re seeing is a classic timezone conflict between UTC and South Korea’s UTC+9 offset where the rounding and the individual “change” commands aren’t syncing perfectly.

To fix this you should use the clean slate method which means rounding the value down to the day first to effectively wipe the time to 00:00:00 and then simply using the plus hours operator to add 9.

By rounding to the day instead of just the date you ensure all minutes and seconds are completely neutralized before you set your specific time. This prevents those stubborn ghost minutes from reappearing when Bubble converts the data for your local display in South Korea.

Just make sure your app settings or your formatting expression are also set to use the current user’s timezone so the 09:00 you saved is exactly what you see on the screen.

3

This is a Bubble timezone issue @phb0222

Bubble processes dates in UTC internally. :rounded down to date rounds to midnight UTC, for you in KST (UTC+9), that’s already 9:00 AM local time before you even apply “change hours to 9”. The stray 4 minutes are likely surviving because change minutes to 0 is being applied in the wrong order.

Quick fixes:

  • Go to Settings → General and set your app timezone to Asia/Seoul.
  • In your :formatted as expression, explicitly select Asia/Seoul as the timezone.
  • Instead of chaining change hours/minutes/seconds, try: :rounded down to day + : + 9 hours , much more reliable.

The + 9 hours approach + correct timezone setting should fix it immediately.

4

The extra minutes are almost certainly a timezone offset issue. Bubble stores dates in UTC, so when you set hours to 9 and save, the value getting written to the DB is 9:00 UTC — but when you format it back for display, Bubble is converting to your local timezone (KST, UTC+9), which shifts it to 18:00. The reverse can happen too depending on how the rounding/formatting is applied, and fractional hour offsets can show up as unexpected minutes.

A few things to check:

  1. In your app’s General settings, what is the timezone set to? Try setting it to “Asia/Seoul” if it isn’t already.
  2. When you format the date for display, are you using :formatted as with a specific timezone, or just the default?
  3. Is the 04-minute offset consistent every time, or does it vary?

The consistent +4 minutes makes me think there might be a secondary offset or a rounding step happening before the hours/minutes are being zeroed out. Try removing the “rounded down to date” step and just applying the hour/minute/second changes directly to see if the minutes clean up.