Hi Team,
A flow that was running fine for months has suddenly failed with this error: "The specified object was not found in the store., Default folder Inbox not found".
Purpose of this flow: Whenever a report arrives in a shared mailbox (Inbox), take this report and place it in a sharepoint folder.
Any help for fix will be much appreciated! Thank you!
Make sure you are not using the trigger even TO field since this could be multiple or the account could be cc.
I found my issue had to do with syncing to azure exchange online. When I created the Shared Mailbox I was using on premises, I change the default email domain to a newer domain from rebranding (ie @olddomain.com > @newdomain.com). This is fine if you wait a while and make sure IT ACTUALLY SAYS the new domain when you migrate the mailbox to exchange online. You can see this when you set up the migration job at the "manually add users to migrate" step. It may take over 24 hours to sync, but just be sure it says the new domain when adding shared mailbox here. I have not been able to fix it after the fact and had to create new mailboxes.
I am also having the same issues with this trigger. Does anyone have any solutions for this?
Same issue here. This makes the flow template "Create a file in SharePoint when an email is received in a shared mailbox" useless for me.
@v-yujincui-msft
Is there possibly an update concerning this issue?
This seems to be a long term issue for microsoft flow trigger on new emails in shared mailbox that has not been fixed. None of the "solutions" (and rebuilding the flow from scratch is not a solution) work reliably. Permissions are all fine, service account can open mailbox in outlook 365, etc. Other similar flows work fine. The only "fix" i have found when this happens is to create a new mailbox and hope it does not have the same issue. Saving a copy and using that only worked for me once so far during our migration to cloud. I have about 200 mailboxes to configure since "email enabled libraries" are not a thing in SPO. Very frustrating. Almost as bad as not allowing parameters in certain flow functions (boo).
Hi @karkumar ,
Does this problem still exist?
Maybe you could try to create a new connection or recreate your flow, then try it again.
In addition, here are some links for your reference.
https://www.enjoysharepoint.com/the-specified-object-was-not-found-in-the-store-power-automate/
Sorry for any inconvenience.
Best Regards,
Charlie Choi
WarrenBelz
146,660
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,999
Most Valuable Professional