Target Session Invalid Error: Add a Row to a Table (Flow)

[BabyYoda1]

I've attached some screenshots of the issue I'm having with this flow. The flow is simple and it just adds a row to a table in excel after a MS Form is submitted. 

The flow has worked for a while but it has failed the last week and a half for some reason. The error message I'm getting is 400: BadRequest. It says the "Target Session is Invalid". I'm not sure how to fix this issue. I've tried moving the excel file to a different location, I've checked the connections, I've looked inside the excel file for issues and I've completely rebuilt this flow to see if there was an issue in the flow itself. Everything works up until the "Add a Row to a Table" step. One thing I noticed was that the tables were not showing up in the drop down of the in the "Add a Row to a Table" step so it seems there is an issue with even pulling the tables. Once the excel file is selected it should allow me to select a table. In my circumstance I'm using a dynamic value but I should still have the option to select a table. 

Can anyone help figure out what the issue is with this? Appreciate any help! 

Flow errorNot pulling table names

[eb17]

Were you able to solve this error? I'm having the same issue with my flow too.

[David2831]

Same problem as well, started a week and a half ago.  Problem is only happening with one excel file, a template that is copied and filled out daily by my users.  My archive of thousands of these logs all worked before, but now none of them read in my flows, but if I target other excel files it works fine.  And all these files have been read before.

Tried making a new flow from scratch to test with, same issue with test flow. Both excel 'Get Tables' and 'List rows' actions fail.  Also tried copying the template or logs from the archive to a OneDrive folder to eliminate and permission issues or SharePoint limitations.  Still no luck.

Interested in any solutions.  Most of what I have seen says 'Wait and it will start working again'.

[BabyYoda1]

Yeah, in my case there was an issue with the file itself. I saved it in OneDrive under a different name and in the general document library and it started working. It didn't like accessing the directory I had it in. 

[bu11frogg]

I had the same issue in a couple different flows, all with Excel files stored in SharePoint. I had to wrap the Excel flow action in a "Do Until" which would continue with the flow once "Status" of the Excel action = 200 (success).  Inside the Do Until I added a 5s delay before the Excel flow action.  That made those flows take longer to run, but resulted in them completing successfully.

[eb17]

Thanks for the suggestion! Could you include a screenshot for how the flow looks with the do until condition?

[bu11frogg]

Yes, of course, I should've definitely done that.  I learned this from somewhere else in the forum (pretty sure), but I can't find it right now, so I'll show how I'm using it in a couple different places.  I have never tried a status other than 200.

Here's an example with Excel, which absolutely fixed this flow for me:

Here's another use case where deleting a system-generated list attachment sometimes failed; this fixed it.

The 2nd example is easier to see where the "Status code" comes from.  It's not in Dynamic content, so you have to construct it like this:  outputs('Delete_attachment')['statusCode']