error importing flow

[Anonymous]

I have a flow that works great in a sandbox environment.  I am unable to import it into another sandbox environment - I get an error:

Flow client error returned with status code "BadRequest" and details "{"error":{"code":"FlowMissingConnection","message":"The flow is missing a connection for api 'shared_office365'. Reauthenticate the connection or remove from the flow and re-save."}}".

(This message is found in the ErrorText column of the Components tab in the import log).

I don't know how to fix this.  Has anyone experienced this and have ideas on how to fix?

[v-alzhan-msft]

Hi @Anonymous ,

The error message told that the flow miss connection?

Have add connection to actions in the flow when you import the flow?

You need to select a connection during import flow.

Best Regards,

Alice

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Thank you!

I'm not familiar with the screen you're showing here.  How did you access it?

[Jcook]

Hi @Anonymous 

How are you trying to get the flow into the other Environment?

The steps should be:

=> Export Flow

=> Import Flow

Check out this awesome video from Jon L:

https://www.youtube.com/watch?v=K7_xWJvEPUc

[Anonymous]

Thank you!  I see now that Alice, in the earlier response, was not using a solution to export/import.  I was told to use solutions for flows!

Right now, I'm fighting between managed/unmanaged solutions.  Neither is working when I get to the target environment.  I cannot publish the solution once I get there (whether managed or unmanaged).

Do you recommend NOT using a solution?

Jon Levesque comments about another video that uses solutions, but who knows yet if that really applies to what I'm doing...

[Jcook · Accepted solution]

@Anonymous 

So solutions are great!

However I have had some troubles with Importing them with Flows in the past.

For one you need to have elevated permissions in the target environment.

What I do is only have the flows in the solution if absolutely necessary. Even if you have a CDS (Current Environment) Connector being used. You can save the flow as Save As and take outside the solution before importing into the target env.

That being said. Once MS Team has the tools to have full ALM inside DevOps pipelines (Which only work with solutions) that is when I will be only using solutions. Than solutions will be the only way to go  

[Anonymous · Accepted solution]

Yeah, wow, that worked!  I imported the solution, opened the flow and did a 'save as' to pull it out of the solution.  Then, I was able to publish and turn it on.  Thank you, thank you.

I really appreciate the assistance.   There is a lot of information available about how to do things with Automate or Dynamics - but not so much about how to figure out what's wrong when things don't work.

(You wouldn't have experience with pulling the url of a Dynamics page, using CDS, into a flow would you?)

[Jcook]

@Anonymous 

That is awesome 😀

Please mark my post as your solution if I solved your problem. For your other question. I recommend, creating a new post, this will ensure others with same issues are able to find it.

If you want, you can also tag me in the post, and I can try to assist.

Thanks 

[mbk]

I have exactly the same problem.

(I have a solution with a lot of flows - when I import the solution I get this error for every flow that uses the Office 365 Outlook connector e.g. to send an email)

What I would like to know is if this is really the expected behavior?

- Is it really to be expected that a solution will not work after importing to a new environment, if the solution contains Flows that uses the Office 365 Outlook connector? I have tried to create the connections in the target environment before importing the solution, but I still get the error?

Kind regards

Michael

[charles_ross_oh]

In my case I had to open up the machine connection (in the cloud flow, under Data > Connections) within the imported flow and re-enter the machine group and login credentials, because (as the warnings say) moving to the different environment will break any connections from the original environment.

One of the things that makes an environment unique is a specific machine group name.