Daylight Savings Time - Discrepancies (1 hour out)?

Ask the community
1

Hi

I’m in the UK and using Airtable as the data source. Project managers build UK-based events which are stored in the data source - setting start date / times. Users can then view this information and accept or decline events.

When building the project, the dates are entering correctly on the user side:

Screenshot 2025-01-14 at 16.08.26
Screenshot 2025-01-14 at 16.08.261082×342 18.8 KB

When saved, it’s saving to AirTable as an hour out if the date is on/after the 30th March (when the UK British Summer Time begins - moving clocks forward) - meaning when users view it, it’s pulling through the time as one hour out in some places.

Any suggestions, please?

2

I haven’t had chance to explore and test this myself but does it help to check Airtable’s time zone settings and subsequent interaction with Softr.io?

3

There are settings in Softr as well as in Airtable best if they match either fixed or to user’s timezone

4

Thank you. Solved:

  • Set ‘same timezone for all collaborators’ in both AirTable and Softr
  • Set timezones the same in both AirTable and Softr - in this case, both to Europe/London.