'shared_office365 doesn't exist'

[bean]

Second time posting this issue. The first time I hadthis issue I simply remade my flow. However, I'd really rather not do that again as this flow is a lot bigger, and I really can't be.... bothered. 

Here is a screenshot of the error I am getting:

It's Friday, and I'm tired. I hope someone knows what the problem is and touch wood it's an easy fix.

Thanks in advance!

Sean

Hope you all have a good weekend.

[v-monli-msft]

Hi @bean,

Can you share the detailed configuration about the fields in this "Send an approval email" action? As the error occurs on this action.

Regards,

Mona

[bean]

Hey Mona, thank you for your reply. 

Since, I have started on a new solution using modern approvals (Which so far is working a lot better - https://flow.microsoft.com/en-us/blog/introducing-modern-approvals/ )

I believe the fields were filled correctly:

email: andrewk@mycompany.co.nz (When typing in this field it would suggest an email...)

title: Change Request (these were set in a variable further up to save manually typing them in to each approval email)

options: Approve, Decline

body: please choose - this is a test

This was working. But it eventually crashed. I was hoping someone else  might have had the same problem, and had an easy fix. 

As for now, I will be working on another flow using the modern approval - Hopefully that works better!

Thanks again,

Sean

[martinav]

I'm having the exact same issue with a strikingly similar error.  Mine is just a very simple email notification.  Scenario is that it worked yesterday, I left the building, triggered it, and it failed... failing ever since.  I recreated the step, reconnected to my connection, etc.  Flow works fine until the email then it bombs.  I got nuthin... ideas?.  

[jrideoutswca]

I get the same error. It works when I am the one initiating the Flow, but not for any of my users, regardless of permissions.

[martinav]

@jrideoutswca,

Did yours ever work for others?  Or, is this a new flow that you have not yet gotten to work correctly?

[faustocapellanj]

Hi @martinav and @jrideoutswca

I've seen these error before, but nothing to pinpoint the issue to fix it. The only way I can get around that is by exporting the Flow and re-importing again with a different name. I know this is more of a workaround and not a permanent fix.

Regards,

Fausto Capellan, Jr

[jrideoutswca]

@martinav and @faustocapellanj - 

I just got this figured out yesterday. @faustocapellanj is correct in that it has something to do with the Flow needing to be "reset" in a way. Based on my Flow, I had to go back into my PowerApp, disconnect all data sources except for the SharePoint source, publish, then re-add the Flow to my button. It seems to work as expected, but I've only run a few tests so far. I hope to more today. 

All I can say is that make sure you copy your OnSelect fx before you remove the connections or readd the flow. 

Thanks!

[martinav]

@faustocapellanj,

Does this method also remove any superfluous variables that may have accumulated during the life of the flow?  I have a few that I would really like to get cleaned up.  I have yet to venture into the export/import methods.