Multiple Errors with saving

[mjackson]

Hello, I have a flow that has been working great until today. My last save was about 23 hours ago with no saving issues. I went to do a quick demo, and only changed recipients of the emails for the purpose of testing.

I could not save it without getting the following error: " Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'sharepointonline' operation 'GetTable' failed with status code 'NotFound'. This may indicate invalid input parameters. Error response: { "status": 404, "message": "List not found\r\nclientRequestId: 473866e4-dbab-4a18-a910-55aaee63db6a\r\nserviceRequestId: 473866e4-dbab-4a18-a910-55aaee63db6a" }'" Even if I refresh the page and save it with making no changes I am still getting the same error.

Each time I refresh I get a new connector error in the flow checker as well: "Invalid Connection. Please choose a connection" and when I click on it, a connector opens with the following error message: "Encountered internal server error from Azure Resource Manager. The tracking Id is '0577672c-3c16-4867-a86d-c991a349be09'." Each time I reload the flow, the connector that has the error is different, for example a simple send and email from outlook or update SharePoint list.

These are connectors that I know are clear of errors since we have done so many testing. I am wondering if this is a tenant issue. I noticed on the support page it says: Microsoft Account users (non-Azure Active Directory users) in Asia, Australia, Canada, France, India, Japan, South America, UAE, United Kingdom were unable to save flows starting on 2021-01-06 17:02 UTC. The issue was mitigated on 2021-01-11 19:50 UTC and all Microsoft Account users should be able to save flows successfully. I believe this was only a few minutes ago, but I am in the US and still having issues.

I tried to save another running flow that I have and had no issues. Any insight would be greatly appreciated

[v-litu-msft]

Hi @mjackson,

10 hours after, couldn't your Flow still save?

If still couldn't, I think maybe it is caused by the first issue, the list not found. You could delete these invalid connections to void the action will connect these connections automaticlly.

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

[mjackson]

Hi @v-litu-msft thank you for your reply,

Yes, I am still having issues with the 404 error. I have over 100 connections in the flow and I would really prefer not having to go back and delete half of them to fix this. I only have one list associated with the flow and it has worked since its creation early last year. I am not sure what the root of this issue could be.

I wish it could tell me the exact connection that is having an issue, rather than just "get table". Any insight to what connectors that could be associated with?

[mjackson · Accepted solution]

I went through and deleted all of my SharePoint connectors and re-implemented them. That has fixed the problem and I can now save. Thanks!

[TrudyZ]

Can you explain to me what you mean by Sharepoint connectors?