Hmm, I should definitely be based in that timezone. I get this from a record I’ve added at 7:35pm Berlin time back in _ctime: 2022-01-21T18:35:45.320+00:00
Any place I can / should check the timezone setting explicitly?
So for self-hosted SeaTable instances you could check your TIME_ZONE environment variable (set in the SeaTable docker-compose.yml file when following their instructions). I didn’t get any response from the SeaTable team as to how to query the SeaTable server time zone through their API or how their cloud serves determines which time zone to use.
So I’ve raised the below PR letting n8n users manually set the time zone as part of the SeaTable credentials in n8n:
I will let you know once it’s released (and you should then be able to simply set Europe/Berlin as the time zone to be used by the trigger).
That’s awesome, thank you for your effort @MutedJam ! Greatly appreciated.
I can confirm that setting TIME_ZONE=Etc/UTC in Seatable Selfhosted does trigger correctly in my n8n when new rows are created! Thanks for that solution / hint!
i create a new base at seatable, recreate a new trigger node and it working with TIME_ZONE=Etc/UTC
I see the option to set timezone in credentials now, but how do I use it?
Should I remove the TIME_ZONE variable from seatable? Or set it to Berlin and my credentials as well? Somehow it’s again not triggering…
EDIT: Ok could be that my seatable database migrations failed, as I see different variables returned when I create a new base… Will inquire and report back
EDIT2: Nope, curiously I get “_ctime”: “2023-04-21T17:00:19Z” when I call the column _ctime or don’t have the column at all in seatable, yet when I call it sth else it returns null (for example called “timestamp”)…
EDIT 3: When the seatable credential timezone is empty AND my workflow timezone is set to Azores (GMT-1) instead of Berlin (GMT+1) it triggers. Seatable docker-compose TIME_ZONE=Etc/UTC
When I rename the _ctime column to timestamp it still triggers, but then shows null as the value in the execution data.
EDIT 4: Ok probably just use Webhooks instead like referenced here
I have set it aside using a workaround. Just today I wanted to finally get it working again, but I can’t seem to. Tried setting my Seatable self-hosted version to TIME_ZONE=Etc/UTC and also tried TIME_ZONE=Europe/Berlin. I tried setting my n8n seatable credentials to Europe/Berlin.
This is really frustrating as I have the feeling it should be sth super simple, but somehow I can’t see where I’m going wrong…
When just hitting Execute Workflow the timestamp of 2022-11-20 00:08:53 displayed in Seatable does not return in n8n but shows null, only if I query that table via the node do I get that value as 2022-11-19T23:08:53.936+00:00
My workflow timezone is set to Standard / Berlin.
Any thoughts / ideas what I do wrong or what I could check, try, etc @MutedJam ?
Seatable self-hosted Developer Edition: 3.5.0
N8N self-hosted: 0.222.3
I also noticed that I have an execution running forever (I think whenever I recreate Seatable docker container), and when I try to stop it it says
Problem stopping execution
The execution ID “1641” could not be found.