cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
willyzh
Advocate II
Advocate II

Failed to import Flow

I was trying to import a Flow from one environment to a new environment. The import process failed with the errors shown below. The Flow works successfully in the old environment. But now it's saying it has issues to get table. In the Flow, there is a step for "Get items" from a SharePoint list. Could that the be the source of the error? If so, how can I debug and solve it? (I couldn't just delete that step because the steps afterwards will rely on the results of "Get items".)

 

Error:

Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'sharepointonline' operation 'GetTable' failed with status code 'Unauthorized'. This may indicate invalid input parameters. Error response: { "error_description": "Exception of type 'Microsoft.IdentityModel.Tokens.AudienceUriValidationFailedException' was thrown." }'.

flow.PNG

 

I have seen this post, which got a very similar error message, but that was happening when trying to save the Flow.

 

Thank you in advance!

12 REPLIES 12
v-bacao-msft
Community Support
Community Support

 

Hi @willyzh ,

 

I did a similar test, but I was unable to reproduce such an issue.

Please try to update the connection in the current Flow first, then create the same connection in the new environment in advance.

Finally, try importing this Flow again and see if a similar issue still exists.

 

Best Regards,

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

HI @willyzh 

 

I think the key is "unauthorized" in the error message. Creating the connection before can solve this issue as mentioned by @v-bacao-msft, I recommend creating a simple flow with just a button trigger and a "Get Items". If you reach the information then you're sure that you have permissions. If not you can work on that until it works. After the connection stuff is organized then you're sure that the connection will work when you import the flow.

 

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

willyzh
Advocate II
Advocate II

Hi @v-bacao-msft and @manuelstgomes ,

 

Thank you very much for your replies.

 

The challenge is that the we are using different accounts to set up the connections in the old and new environments. And the SharePoint lists are also located indepedently in these two environments.

 

I have tried to create a new Flow with just "Get items" and it worked in the new tenant environment. But the import process still failed afterwards.

 

One side note is that I have successfully imported a PowerApps package and the Flows included in that package to the new tenant. Those Flows were succussfully created and some of them have "Get item from SharePoint list".

 

Thanks again. Hope you to hear from you soon.

 

Best regards,

Will

lbabativa1
New Member

Hi @willyzh 

 

I had a similar problem, Sometimes when you import a flow some activities does not update properly, you need to look for the sharepoint action and update the json schema.

Microsoft.Flow/flows/{GUID}/definition.json in the .zip file.

 

Search SharePoint action and the schema must be like this

Folde1r.png

If is different you need change this schema like I did show.

 

Regards,

Luis Babativa

If this post helps, then please consider Accept it as the solution to help the other members find it more

Bonsoir @lbabativa1 ,

 

Merci pour votre réponse qui semble apporter des solutions concrètes.

Je rencontre le même problème et j'aurai besoin de précision quant à votre proposition.

Vous indiquez où faire les modifs: Microsoft.Flow / flows / {GUID} /definition.json dans le fichier .zip.

Mais quelles modifs doivent être réalisées?

Merci d'avance pour votre aide,

Cordialement,

Mélanie

Jcook
MVP

@willyzh 

 

is the flow in a solution?

 

What you can try is to export the flow and re import the package into the same environment. Than export again


Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





Bonjour @Jcook ,

De mon côté j’ai déjà essayé cette solution et j’obtiens le même résultat.

Echec.


Dans solution, 1 app, 6 flows. 4 passent parfaitement et pour les 2 autres c’est impossible.

pourtant, j’ai des actions SharePoint dans les 6.

incomprehensible..

@willyzh Can you please tell us. How you managed to import. I'm Having same issue and got stucked.

Hello @wan237 

 

Please start a new post, and tag me using the '@' symbol and my username Jcook.


Did I answer your question? Mark my post as a solution!

If you like my post please hit the Thumbs Up


Proud to be a Flownaut!


Check out my blog for Power Automate tips,
tricks, and guides
FlowAltDelete





@wan237 ,

I was getting the same error and was able fix it by updating the definition.js file in the exported zip file.

What I was trying to do is export a flow from one site and import it to another site using a different username.  The new username does not have access to the original site.   The definition.js had references to the old site and the import procedure was having problems authenticating. 

 

My solution was to edit the definition.js file and replace the SharePoint URL and List ID with the new site information.  The definition.js file is in the lowest folder in the exported zip file and is defined under parameters

"parameters":{"dataset":"https://<URL to SharePoint site>/","table":"B582B199-6500-4F76-8627-C08D770204A6"}

I replaced the URL and list ID (defined under table), saved the definition.js file and copied it to the zip file.   Afterwards I was able to successfully import the flow.

 

Hi 

 

Trying out @eshen solution I just get an unknown error when I try to upload the package after I made the changes to the definition.json file.

 

What really strikes me here, is that making changes to that file or any file in the package would even be necessary? 

Moving App's between tenants should not be this difficult!

 

It makes sense thoug, that the reason it fails to begin with, is because the references in the file are pointing to the wrong URL and therefore we recieve an 'unauthorized' error. But if this is in fact the case, it should be something you get to change during the upload process, otherwise this export/import feature is more or less useless.

YousufK
New Member

Hi

So I had the same issue when I tried to import a new flow. It seems that the authorisation is in fact the key issue as was highlighted by another user on this thread.

 

so what I did then to fix the issue was to create new connections in my new flow workspace, with the accounts of the old workflow I was importing. so for example, if I exported a flow from Account Username1, and then is importing it into the flow workspace of Account Username2, I first added a new connection for each element of my flow into my flow workspace for account username2.

 

This meant going an adding a connection to flow workspace for user account Username2 for both Forms and SharePoint in my Manage connections list, but when asked which login to use, I used Username1. I repeated this for each connection type I needed.

 

then, I went back to the flows workspace and tried importing again. On importing, when asked to select a connection, I selected the connections linked to account username1. this then allowed me to successfully import my flow.

 

Hope this helps.

 

Thanks.

Helpful resources

Announcements
Microsoft 365 Conference – December 6-8, 2022

Microsoft 365 Conference – December 6-8, 2022

Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.

Users online (3,011)