Unanswered

Office 365 Groups Mail Connector - Stopped Working this week?

(6) Share

Report

Posted on by gmitchell1

Hi, for months, I have been using Flows that are triggered by new e-mails received in Office 365 Groups Mail inboxes. However, as of this weekend, the Flows stopped triggering upon new e-mails. I'm hoping to understand if this is a known issue? Below are some of the checks I've done:

- The Connections show up as "connected", including my firm e-mail connection to Office 365 Groups

- When I view the group mailbox, I see that the messages are there.

- I tried multiple different Groups mailboxes with the same issue

- My personal inbox "get email" flows are working. When I hit resubmit on some old flows, all other connections are working.

Thanks,

Greg

Categories:

Using connectors

I have the same question (0)

All responses (13)

Answers (0)

Sort by

maximogc 4 on at

Like (0)

Report
Copy link

Link copied!

having same issue atm

Was this reply helpful? Yes No
MatheusSilvaSar 12 on at

Like (0)

Report
Copy link

Link copied!

I’m having the same issue in logic apps. So far after a long investigation I noticed that the trigger behavior change. If you open the trigger details in the output session and in the location field you have the graph api call to retrieve the conversation (email) from the groups. If you go to the end of that URI you will see that since the weekend the trigger is using the SKIP parameter and every time that you send a new email that skip is incremented. Forcing the trigger to always look to the wrong set of emails to collect and trigger.

please confirm if you have the same behavior from your side.

Was this reply helpful? Yes No
amby0430 9 on at

Like (0)

Report
Copy link

Link copied!

I am having this same issue, I have tried removing the connection and re-authenticating. Removing the trigger and re-adding as well, but nothing is working. Let me know if anyone has seen an update on how to resolve.

Was this reply helpful? Yes No
gquilop 9 on at

Like (1)

Report
Copy link

Link copied!

Same issue here. Checked everything and tried the above as well before finding this thread. Hoping this gets resolved or a workaround is found soon.

Was this reply helpful? Yes No
gmitchell1 40 on at

Like (0)

Report
Copy link

Link copied!

Thanks, Matheus. I don't see the SKIP, unfortunately, but I'm not sure I'm looking in the right spot.

My reaction to all this is to try to move to Shared Mailboxes exclusively. I speculate the Office 365 Groups Mail has not reached critical mass to receive the necessary attention/support.

Was this reply helpful? Yes No
dev85 44 on at

Like (0)

Report
Copy link

Link copied!

Hey @gmitchell1

I'm having the same issue, could you please explain in a deeper way how the Shared Mailboxes approach will work?

Was this reply helpful? Yes No
phaidara 3 on at

Like (0)

Report
Copy link

Link copied!

Hello,

Same here.. I've been using the Office 365 Groups Mail Connector for months now, without any issues.
It suddenly stopped working last friday..

Let me know if anyone has any update on how to resolve this issue.

Was this reply helpful? Yes No
Claudio 12 on at

Like (1)

Report
Copy link

Link copied!

great. i've been using for years and now stopped working. Looking what to do. In the message center there are some notifications about problems with group workloads

"We've reverted the previously mentioned deployment, confirming that it caused a compatibility issue for Graph API for requests concerning group workloads and conversation data" - MO778766
Wonder if it has with this. I don't know what to do since this flow is for me handling hundreds of emails every day,.. now hmm.
If not above, then maybe something else to do? ideas anyone

Was this reply helpful? Yes No

MatheusSilvaSar

12 on at

Like (4)

Report

Copy link

Link copied!

Microsoft recognized the issue under the alert MF779969. they are now working on the fix. This is what the alert is saying:

Users don't see flows triggered for the Office 365 Groups Mail connector when a new email arrives to a group

ID: MF779969

Issue type: Advisory

Status

Service Degradation

Impacted services

Microsoft Power Automate in Microsoft 365

Details

Title: Users don't see flows triggered for the Office 365 Groups Mail connector when a new email arrives to a group

User impact: Users don't see flows triggered for the Office 365 Groups Mail connector when a new email arrives to a group.

Current status: We've determined an update to the underlying service infrastructure that the Office 365 Groups Mail connector relies on to execute the "When a new email arrives to a group" trigger contains a code issue. We're developing a code fix to remediate the impact.

Scope of impact: Your organization is affected by this event, and it impacts any users expecting to see Microsoft Power Automate flows triggered for the Office 365 Groups Mail connector when a new email arrives to a group.

Start time: Friday, April 12, 2024, at 12:00 AM UTC

Root cause: An update to the underlying service infrastructure that the Office 365 Groups Mail connector relies on to execute the "When a new email arrives to a group" trigger contains a code issue.

Next update by: Friday, April 19, 2024, at 8:00 PM UTC

Was this reply helpful? Yes No

Claudio 12 on at

Like (0)

Report
Copy link

Link copied!

many thanks. was looking too much inside the code to see what happened even if noone has modified anything. 😉 fortunately just looking.
This is really creating organizational frustration of course many things are dependant of this. I'll need to code a workaround to just go in in a schedule and fetch all emails and send the conversation ids through my child flows. fortunately using child flows for most so i just need the conv id and group id to pass through. but sucks
thanks!

Was this reply helpful? Yes No