Power Platform Community Forum Thread Details

Issue with Flow Adding Attendees to Calendar Event but then Sending Cancellation

I have several flows set up to add attendees to an existing Outlook event when a column within a SharePoint List changes to "Yes." If you go one by one, it works fine. However, we need to be able to bulk update and this is where the issue comes in. The flows are showing success to have added the new attendee, and I can see the calendar invite in my sent box; however, then there is a cancellation every so often. When looking at the calendar event itself, it appears as though only about half of the attendees are actually being added to the event and not canceled out. I'm truly stumped. I've tried researching and trying different workarounds but nothing appears to be solving the issue. I did turn on concurrency and that appears to have helped, but not fully solve the issue (for example, we tried to add 7 people to the event after turning on concurrency - all were added but only 3 appear in the event itself and the other 4 seem to have gotten a cancellation).

Outlook event settings allow forwarding of the event, but do not require a response as I found that this would cause every attendee to receive updates anytime someone new was added.

Screen shots of one of the existing flows attached with the expressions in comments! All others are set up the same way. Concurrency is on with max of 50.

Any advice would be super helpful - I'm pretty new to Power Automate and just learning as I go!

@Kate314

I am a little confused but let me try to guess at somethings.

1) this is an FYI, you could create the flow ONLY to run, when it is set to Yes, versus checking all that are modifide. This assumes you haven't done this Trigger Condition, so apologies if you have

2) You said you turned on Concurrency, but you didn't specify if you set it to 1 (value), if not then thats probably your issue. Turning it on but not setting it to 1 is still the same disaster as its off

3) if its not the Concurrency, then this seems more like a bug in the Flow, which I cannot see it all, then anything else.

Since you seem to be able to easily reproduce it, have you walked through the Run through a flow history instance, so you can see what values / variables / loops etc you are doing, why it sent cancellations instead of invites.

--This is the most likely way to find your issue. Thats the reason you can walk through them step by step and if you have loops, see every since iteration of the loop and the values used in that loop instance.

But if concurrency is on and <> 1 value or if its not on, you can hose yourself.

If you like my answer, I would really appreciate if you please Mark it as Resolved, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Quick Links

Leaderboard