Grabbing Group Emails - TAKING AGES TO TRIGGER?

[jed76]

Anyone else having any issues with powerautomate today? I've got a process which uses the When a new email arrives to a group trigger and it normally works fine. However, for the past few days it seems to be triggering hours after the email group has received an email?

[LLinx]

Yes, we have exactly the same problem. Over the course of the entire day, exactly 1 email has been picked up from 8 emails that were sent to the mailbox.

Larger thread is already set up here, probably related.

[jed76]

@LLinx  Odd isn't it?! 

They seem to be triggering about 12 hours late!

[ralzayyat]

I have an issue with Power Automation I'm trying to use trigger Type property in condition and set value to is equal to submit but I received below error 

The execution of template action 'Apply_to_each' failed: the result of the evaluation of 'foreach' expression '@triggerOutputs()?['body/triggerType']' is of type 'String'. The result must be a valid array.

What should I do?

[RedNDusty]

Same issue here only everything just seems to have stopped over the weekend. Up until Saturday, we had an automation that was running on average 4 times a day, and now nothing. I've attempted duplicating the automation and I'm able to get 1-2 successful runs before it stops picking up on new emails. 

[jed76]

They seem to be working but they’re hours behind. Mine are starting to trigger from emails sent yesterday!

[RedNDusty]

I'm still not seeing any improvement on my end of things. Have you come across any indication of a cause for this? I'm unable to come up with any answers. 

[kaplanservice]

Having the same issue here. Flow is working but the trigger is very delayed. I just submitted a support ticket and will follow up. 

[jed76]

Great - thanks. It's very odd. I'm used to the trigger being instant but the flow being slow at times, but I've never seen it where the trigger itself is delayed. 

[steeps]

I am also experiencing issues with "When a new email arrives to a group." I opened a ticket that linked here. This was the answer I got: "The Product team is aware of this issue, and they are currently working on it."

[jed76]

Great. I’m still experiencing issues. The flow seems to be triggering but often with a previous email?! 

most odd.

I saw in the HEALTH STATUS that there was issues with slow traffic on Monday but that is now showing as fixed. Hopefully they will get to the bottom of this soon as I utilise this as part of a CRM system to capture email conversations and attachments. 

[jed76]

How do you open a support ticket as I will do the same!

[Tan-M_816]

I am having the same issue, I have had attachments from a Group Email being automatically uploaded to SharePoint based on a condition where the Subject text contains particular words, the attachments are then saved to different folders in the SharePoint  Group.  Everything has been working perfectly until Thursday 11th and suddenly it all stopped. 

[jed76]

Yes - same for me! The odd thing is mine appears to be triggering now and again but with the same email from days ago?! Hopefully they will sort it soon!

[kaplanservice]

hey everyone - Following up on my previous mention of submitting a ticket. This is impacting our production environment and are currently forced to manually deal with all incoming group emails. I heard back from Microsoft Team, I will follow up when I hear more.

This is what they said: 

As I mentioned in our previous call I got in contact with the production team and they are working on a solution for this issue. They were able to identify that the issue is cause by something on the Outlook side and they are collaborating with the team that works on it to solve the issue.

Today the Outlook team got back to us and let us know that it might take some time for the solution to be implemented and go live for users. The said the ETA would be around 1 to 2 weeks.

My team then let me know they have a workaround they are working on that should be able to go live sooner and that they will work on that. I asked for an ETA on the workaround but have not received an answer yet.

[jed76]

Thank you very much for posting this update!

I wonder if when it starts working again, whether the old triggers will start?

[LLinx]

Accidental Doublepost

[LLinx · Accepted solution]

At one of my customers, we were using this connector as well. To avoid the issues, we have switched over to a shared mailbox instead of the O365 group.

We did the following:

• Create Shared mailbox with new name, with flow owner full access
• Activated Folders and Mail Rules on O365 Groups  (MS Documentation) - takes some time, half an hour/hour
• Created mail forward rule from O365 Group mailbox to Shared Mailbox
• Switched trigger in flow to start from Shared Mailbox and updated the rest of the flow to the new trigger where needed.

We chose to make the full switch, since we feel like the Shared Mailboxes are better supported by Microsoft in general, looking at the documentation of the Group Mailbox. (Group mailbox has less guarantee that all triggers will run when a lot of mails are coming in a short period, etc.)

[jed76]

Thank you. I must admit, originally when I was researching this, I tried it with a share mailbox and it did seem much easier. 

[jed76]

As an easier solution, would it not be easier to just create a new office shared mailbox with a different name altogether and then just trigger with that email address instead?