Power Automate flow has suddenly stopped working

[rorulon]

Hi all, not sure if this is the right place to be posting this but I couldn’t see a dedicated Power Automate community or group on the list

We’ve been using a Power Automate workflow for a few months now to send scanned documents to a SharePoint area so that our whole admin team can see that one place and process the documents accoridngly. The process works like this:

• The user scans a document.
• The document is sent, using the email address scanner@domain.co.uk to a shared mailbox depending on the location of the office (postin.liverpool@domain.co.uk, postin.manchester@domain.co.uk, etc.)
• When the email with the attachment arrives, this triggers the flow. It will take the attachments, the create a file in the corresponding SharePoint location (Post In - Liverpool, Post In - Manchester, etc.) that has the file name and content of the attachment.

This has been working without issue for a few months now, but suddenly it has just stopped. I’ve been doing some investigating and it looks like the emails are being sent from the scanner, and arriving in the postin mailbox, but then the trigger isn’t activating from there to create a file in SharePoint.

This is a picture of the flow in Power Automate:

And it looks like all permissions are fine, the account we use for this (an IT automation account set up for this purpose) has full access to the Sharepoint area and the shared mailboxes, and we haven’t changed anything since we set it up a few months back and tested that it worked.

Whenever I go onto the flow now it tells me “There’s a problem that needs to be fixed to trigger this flow. To see more details, open Flow checker,” I do this and I get the following in the error details:

The specified object was not found in the store., The process failed to get the correct properties.
clientRequestId: ec4cf1d7-056b-48bc-b67a-d83b23c522b9
serviceRequestId: c0d06e54-9b5f-4089-b8b9-6e8b547bdbe7

And the following as the raw output:

{
    "statusCode": 404,
    "headers": {
        "Pragma": "no-cache",
        "x-ms-request-id": "c0d06e54-9b5f-4089-b8b9-6e8b547bdbe7",
        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
        "X-Content-Type-Options": "nosniff",
        "X-Frame-Options": "DENY",
        "Cache-Control": "no-store, no-cache",
        "Set-Cookie": "ARRAffinity=0ed1bcb78d196a270aeab0b5cad700a84c78dc6546406fc73f38e51d72717001;Path=/;HttpOnly;Secure;Domain=office365-ne.azconn-ne-01.p.azurewebsites.net,ARRAffinitySameSite=0ed1bcb78d196a270aeab0b5cad700a84c78dc6546406fc73f38e51d72717001;Path=/;HttpOnly;SameSite=None;Secure;Domain=office365-ne.azconn-ne-01.p.azurewebsites.net",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "false",
        "Date": "Fri, 10 Dec 2021 12:11:23 GMT",
        "Content-Length": "614",
        "Content-Type": "application/json",
        "Expires": "-1"
    },
    "body": {
        "status": 404,
        "message": "The specified object was not found in the store., The process failed to get the correct properties.\r\nclientRequestId: ec4cf1d7-056b-48bc-b67a-d83b23c522b9\r\nserviceRequestId: c0d06e54-9b5f-4089-b8b9-6e8b547bdbe7",
        "error": {
            "message": "The specified object was not found in the store., The process failed to get the correct properties.",
            "code": "ErrorItemNotFound",
            "originalMessage": "The specified object was not found in the store., The process failed to get the correct properties."
        },
        "source": "office365-ne.azconn-ne-01.p.azurewebsites.net"
    }
}

Googling about this I’m not finding anything concrete to help sort the problem, hopefully you guys can help me make sense of this and straighten it out, or at least point me in the right direction, cheers!

ADDITIONAL INFO

Thought I’d drop this in as well, this is the raw input for the trigger:

{
    "host": {
        "connectionReferenceName": "shared_office365",
        "operationId": "SharedMailboxOnNewEmailV2"
    },
    "parameters": {
        "mailboxAddress": "postin.liverpool@domain.co.uk;",
        "folderId": "Id::AQMkADAzOWE3YzM3LTUwODUtNGIxNy05YjU2LTU5Yzc1NzQ0ADIwMTYALgAAA4nLZFahbgxJsbYM4YpcpG8BAGlqW0ZZYhhPgvIPtbAvwBIAAAIBDAAAAA==",
        "to": "postin.liverpool@domain.co.uk",
        "from": "scanner@domain.co.uk",
        "importance": "Any",
        "hasAttachments": true,
        "includeAttachments": true
    }
}

…and the raw output for it:

{
    "statusCode": 404,
    "headers": {
        "Pragma": "no-cache",
        "x-ms-request-id": "7e0610ec-9fa5-4244-ac33-3c4028f876e9",
        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
        "X-Content-Type-Options": "nosniff",
        "X-Frame-Options": "DENY",
        "Cache-Control": "no-store, no-cache",
        "Set-Cookie": "ARRAffinity=23a207a325cefe4d6899a2c70a1923112e0754fee759f0fb1e28c8e77f4cc3d5;Path=/;HttpOnly;Secure;Domain=office365-ne.azconn-ne-01.p.azurewebsites.net,ARRAffinitySameSite=23a207a325cefe4d6899a2c70a1923112e0754fee759f0fb1e28c8e77f4cc3d5;Path=/;HttpOnly;SameSite=None;Secure;Domain=office365-ne.azconn-ne-01.p.azurewebsites.net",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "true",
        "Date": "Fri, 10 Dec 2021 12:52:34 GMT",
        "Content-Length": "614",
        "Content-Type": "application/json",
        "Expires": "-1"
    },
    "body": {
        "status": 404,
        "message": "The specified object was not found in the store., The process failed to get the correct properties.\r\nclientRequestId: bb674638-7f69-476e-8c3c-cf05dbc77867\r\nserviceRequestId: 7e0610ec-9fa5-4244-ac33-3c4028f876e9",
        "error": {
            "message": "The specified object was not found in the store., The process failed to get the correct properties.",
            "code": "ErrorItemNotFound",
            "originalMessage": "The specified object was not found in the store., The process failed to get the correct properties."
        },
        "source": "office365-ne.azconn-ne-01.p.azurewebsites.net"
    }
}

[toddjuenemann]

I have seen similar errors, typically means that a folder or directory may have gotten re-named, check that. Also, on which step of the flow did the error occur, if you go into the flow and do a test of the flow, it will typically show you with step it actually errors on, that helps in narrowing down where the issue is. Also check which connections the step that errors is using, you can do that by clicking on the 3 ellipsis in the upper right corner. I have seen it where a flow step suddenly decides to use a different connections that does not have a permission.

[rorulon]

@toddjuenemann

I have seen similar errors, typically means that a folder or directory may have gotten re-named, check that. Also, on which step of the flow did the error occur, if you go into the flow and do a test of the flow, it will typically show you with step it actually errors on, that helps in narrowing down where the issue is. Also check which connections the step that errors is using, you can do that by clicking on the 3 ellipsis in the upper right corner. I have seen it where a flow step suddenly decides to use a different connections that does not have a permission.

Thanks for the reply, one thing I’ve noticed poring over this stuff is something in the raw input: Under the folderID parameter it says:

"folderId": "Id::AQMkADAzOWE3YzM3LTUwODUtNGIxNy05YjU2LTU5Yzc1NzQ0ADIwMTYALgAAA4nLZFahbgxJsbYM4YpcpG8BAGlqW0ZZYhhPgvIPtbAvwBIAAAIBDAAAAA==",

Yet if I look at previous flows that were successful it says:

"folderId": "Inbox",

Can’t remember if I specified in the wall of text above but the error is coming up during the trigger, specifically this parameter, so I think its linked.

When I tried clearing the Folder field in the flow editor and clicking the folder to select a directory the window that normally appears was instead filled with the error text I posted above, but its weird I haven’t done anything to this flow for months, I’ve checked the permissions and the mailbox itself, and nothing is different there either. I’m considering manually changing the folderID parameter back to Inbox and testing it again, as it seems to be looking at…something that’s clearly wrong

[rorulon]

Managed to sort it, just updating this thread with the solution, its a bit of a nuclear option, and might not be doable for all cases:

• Backed up all the emails in the shared mailbox. Thankfully in my case it was all stored in the base inbox folder, I just copied them over to a folder in my own temporarily
• Removed all access to the shared mailbox in Powershell
• Deleted the shared mailbox
• After a few minutes, created a new shared mailbox with the same name and email address, and added the fullaccess permission for the automation account the flow is created on
• Copied the emails back into this new shared mailbox
• In Power Automate, created a new flow with the exact same conditions and outcome, but pointing to the new shared mailbox instead

TL;DR - The fix was to delete and recreate everything, its now working as intended