Notifications have time shift in the timestamps when using docker-compose

Hello,
we started using notifications for changes in specific columns in a table. It’s a great feature!
There is just one small issue.

When I get the email with the notifications summary the timestamps of the notifications are shifted -1 hour.

The setup is:
Seatable Developer Edition
Docker-compose with the image seatable/seatable:latest (1.7.0)
Environment: TIME_ZONE=Europe/Vienna -> the time in the seatable container is correct
Notification rule:
Records meet specific conditions after modification
Fields to watch - column A, column B
Filter - column A is not empty OR column B is not empty

Many thanks in advance for any hints.

Before our developers answer, I have only one comment: when a notification rule is triggered, it will send a notification in the base editor right away.

image

If this notification was not read in 1 hour, it will be sent via email, if the user has enabled email notification in their personal settings.

image

For example, records met specific condition on 15:30, the notification was sent to the corresponding user on 15:30 inside the base editor.

This user hasn’t read this notification until 16:30. So this is now sent to their email, but as this notification was originally triggered on 15:30, the timestamp in that email would be 15:30.

Unless this is not your case, it is then a bug!

Thanks for your reply!

The scenario plays out exactly as you described, but with one difference at the end.

Records met specific condition on 15:30, the notification was sent to the corresponding user on 15:30 inside the base editor.

This user hasn’t read this notification until 16:30. So this is now sent to their email.
Although the notification was originally triggered on 15:30, the timestamp in that email is 14:30.

OK, so that should be a bug, then! @daniel.pan could you reproduce this problem?

Maybe it is caused by “Daylight Saving Time”.