Unanswered

BadGateway when trying to use Create Event (V4)

(1) Share

Report

Posted on by BijanA

I have a flow that has been running for several months without issue until yesterday. The problem is when I try to use the `Create Event (V4)` action on a shared Outlook calendar.

I initialize the following variables:

Start: 2024-07-02T00:00:00.000Z

End: 2024-07-03T00:00:00.000Z

Title: XXXX Off (15:30-16:30)

And here is the "Code View":

{

"type": "OpenApiConnection",

"inputs": {

"parameters": {

"table": "AAMkADFjNWI2MTgwLTA1Y2YtNDJjZi04ZmZmLTFjMGE4ZjA1OGJhYQBGAAAAAADiyzVW_huQSJiFGaeUpnO0BwBku87Zn7sMRqQPU0RVgd_bAAAAAAEGAABku87Zn7sMRqQPU0RVgd_bAABXXXXX",

"item/subject": "@variables('Title')",

"item/start": "@variables('Start')",

"item/end": "@variables('End')",

"item/timeZone": "(UTC-08:00) Pacific Time (US & Canada)"

"host": {

"apiId": "/providers/Microsoft.PowerApps/apis/shared_office365",

"connection": "shared_office365",

"operationId": "V4CalendarPostItem"

}

"runAfter": {

"Initialize_Title": [

"Succeeded"

]

}

Is this a temporary issue? Is there anything I can do to fix?

All responses (12)

Answers (0)

Suggested answer

TF-24071530-0 on at

Like (1)

Report

BadGateway when trying to use Create Event (V4)

Hello, currently Microsoft support wrote to me that the problem is solved. According to my testing, everything is working again.
Suggested answer

Drooo 4 on at

Like (1)

Report

BadGateway when trying to use Create Event (V4)

I received a message from Microsoft this morning that their development team has resolved this issue. My Create Event (V4) actions are now succeeding.
BijanA on at

Like (0)

Report

Re: BadGateway when trying to use Create Event (V4)

It looks like everyone's issue started around the same time of July 8 and that this is a global issue. Has anyone heard back from Microsoft support?
mimistry 2 on at

Like (0)

Report

Re: BadGateway when trying to use Create Event (V4)

I am having the same issue my flows was working now suddenly stops working but did some further diagnosis and that it works if you point to your own calander but not to a shared calander even when you have full delegation rights this is not a rights issue but definitly something Microsoft has changed somewhere
ChetWeeWax 2 on at

Like (0)

Report

Re: BadGateway when trying to use Create Event (V4)

Same issue here, calendar is owned by another user, but shared will full edit to user running PA. Did not have issues with this for over two years before a couple weeks ago. Get to it Microsoft.
humblpirate 56 on at

Like (1)

Report

Re: BadGateway when trying to use Create Event (V4)

I'm having the same issue. I just put a ticket in with Microsoft support.
BijanA on at

Like (0)

Report

Re: BadGateway when trying to use Create Event (V4)

Thank you for confirming this @ThomasSchneider . So I guess the issue is 100% on Microsoft's end? Is there somewhere we need to submit a bug report to get their eye's on this?

This was part of a flow that is integral to my organization and having to manually migrate every event from my personal calendar to the shared one is a bit annoying 😆
ThomasSchneider 8 on at

Like (1)

Report

Re: BadGateway when trying to use Create Event (V4)

Have had the same issue since July 8th. Even with the MS Graph API, you can only create events in your own calendar, but not in shared calendars.

The Http action runs forever and must be canceled or returns:
"code": "InvalidAuthenticationToken",
"message": "IDX14100: JWT is not well formed, there are no dots (.).\nThe token needs to be in JWS or JWE Compact Serialization Format. (JWS): 'EncodedHeader.EncodedPayload.EncodedSignature'. (JWE): 'EncodedProtectedHeader.EncodedEncryptedKey.EncodedInitializationVector.EncodedCiphertext.EncodedAuthenticationTag'.",

Run the same action via postman returns:
"code": "InvalidAuthenticationToken",
"message": "IDX10612: Decryption failed. Header.Enc is null or empty, it must be specified."

>> Token is well formed and works on own calendar.
BijanA on at

Like (1)

Report

Re: BadGateway when trying to use Create Event (V4)

I narrowed down my issue. The problem is part of the Create Event (V4) part of the flow. If I change to a calendar that I own, it works fine. But when I try to save to a Shared Calendar (that my account did have access to add events as of last week), then it returns 502 BadGateway. I am attaching a screenshot of the flow but it will not make much difference.
I confirmed with my organization's IT that nothing has changed. Other individuals in my org have the same issue where listing events from that calendar works but creating event's does not.

So basically even though my account is able to create events on the shared calendar via Outlook, I get 502 BadGateway when it is done via Power Automate.
Drooo 4 on at

Like (0)

Report

Re: BadGateway when trying to use Create Event (V4)

I have been experiencing the same issue since June 5th. To add some context, in testing I have found I can add calendar events if the step connection is run as myself to my own calendar. If the connection is run as another user (that has permission to add calendar events) it does not work and results in the BadGateway error. I haven't found a way around this yet.

@creativeopinion - Thanks for the suggestion. Toggling back to the old designer did not seem to help my issue.