I have found a bug that I hope gets fixed. I have a PowerApp that manages our companies vacation time. People select start and end dates (we do not do partial days). After an approval the flow creates a calendar event in the employees calendar. November 3rd is the end of Daylight Savings Time. If this calendar event crosses the end of Daylight Savings time we reveice the following error on the create calendar event step: "Your request can't be completed. The Event.End property for an all-day event needs to be set to midnight". The calendar event is marked as an all-day event.
I understand that Flow uses UTC as its default and perhaps there is a way to play with the time zones in the Flow to resolve this but - that should not be nessisary. Flow should be smart enough to handle the end or the begining of daylight savings time. That is why I consider this a bug - this should not be something that users need to account for.
Nope - it is a bug. There are tons of time zones and daylight savings starts/ends on different dates around the world. We should not have to code for each one. If I want an all day event I do not care if the start date is on one side of DST and the end date is on the other side. We should be able to check the All Day button and be done with it.