Showing results for 
Search instead for 
Did you mean: 
Kudo Kingpin
Kudo Kingpin

Office 365 Outlook - Update Event V2 does not accept Dates retrieved in Get Event V2 - UTC not valid

A simple flow

1 - Get Event V2

2 - Update Event V2 using the data obtained in Get Event V2



fails with 

Time zone 'UTC' is not valid.

clientRequestId: 6724eaf0-31c8-4178-8231-2c1ee9f03c25


In my view this is a bug as the Update Event V2 Input should allow the format of the output of Get Event V2


This is the flowThis is the flowDetails of the last stepDetails of the last step

Here the Get Event V2 DataHere the Get Event V2 DataInput in run historyInput in run historyError receivedError received

especially as in create event V2 UTC is an allowed timezone

Create Event V2 allows UTCCreate Event V2 allows UTC




the flow intends to add an additional particpant to an existing Outlook Event

Community Support
Community Support

Hi @ErichH,


Which time zone does your Outlook event set?

Further, which Time zone is your local time zone?


The error message told that there is something wrong with value of Time zone field of “Update event (V2)” action.

I have made a test on my side and don’t have the issue that you mentioned. My flow’s configuration as below:10.JPG

The flow works successfully as below:11.JPG


I have reproduced the issue on my side when I set Time zone property of Outlook event to (UTC) Coordinated Universal Time, it seems that (UTC) Coordinated Universal Time is not supported in “Update event (V2)” action:12.JPG


According to the screenshot that you provided (Here the Get Event V2 Data), you have set Time zone of Outlook event to (UTC) Coordinated Universal Time, please consider take a try to change Time zone property of Outlook event to other Time zone or your local Time zone and check if the issue is solved.


Best regards,


Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Kris yes indeed, when i chose Casablanca or London it works.

Question is why allow utc in create event, but not in update event.

this is inconsistent and confusing. It took me days to figure out what is going on.

this can be avoided.


thanks for considering to fix this.




I am asked whether your reply is a solution.


It is a great hint for a work around how to circumvent the issue, but NOT a SOLUTION for the underlying inconsistency between Create_Event and Update_Event behavior in respect to UTC.



Super User
Super User

I have the exact same issue, that an event can be created using UTC time zone, but the update of the event using Update Event V2 does not accept UTC.


Please fix the issue and get update to be able to use UTC time zone!

Kind regards, John

Same thing with V4

Helpful resources

Process Advisor

Introducing Process Advisor

Check out the new Process Advisor community forum board!

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Carousel April Dunnam Updated 768x460.jpg

Urdu Hindi D365 Bootcamp

Dont miss our very own April Dunnam’s The Developer Guide to the Galaxy! Find out what the Power Platform has to offer for the traditional developer.

Top Solution Authors
Users online (2,067)