Open jpbaril opened 5 days ago
Hey @jpbaril,
We have created an internal ticket to look into this which we will be tracking as "GHC-302"
Hey @jpbaril
It looked ok when I tested it but I may have missed all day event.
What timezone and tz env option do you have set at the moment?
Hey @jpbaril
It looked ok when I tested it but I may have missed all day event.
What timezone and tz env option do you have set at the moment?
- GENERIC_TIMEZONE=America/Toronto
- TZ=America/Toronto
Hey @jpbaril,
I did put in a "fix" for this but when testing what we have now and importing the outputted cal event into different systems it showed the correct dates so it looks like this may actually be ok.
Are you using the ICS file in a calander or do you always manually parse them?
Are you using the ICS file in a calander or do you always manually parse them?
I'm not sure to understand (as English is not my main language).
My_workflow.json event.ics.txt
Generated at: 2024-10-13T09:23:19.921Z
BTW, if event is not an all-day event then resulting end date is ok.
@jpbaril how do you normally use the ICS files? When testing the current dates in a few different calendar applications they load as expected.
Bug Description
The Convert to File Node (Convert to ICS) output "end date" for all-day events is wrong, it's one day later than what it should. E.g. Christmas: DTSTART;VALUE=DATE:20241225 DTEND;VALUE=DATE:20241227
To Reproduce
Expected behavior
To have correct end date, i.e. end date to be 1 day earlier.
Operating System
docker (self-hosted)
n8n Version
1.63.0
Node.js Version
20.18.0
Database
SQLite (default)
Execution mode
main (default)