I frequently run into this issue, and have found it to stem from one of two root causes.
#1: If you're posting to the document library a new "status.xlsx" file each time, then when you "select again the same file" you're actually selecting a different file--even if you're reusing the same filename. In the flow action, instead of selecting a file use dynamic content to enter the fileID and table name as custom values.
#2: Often, it seems that a flow believes an action within a file on OneDrive or SharePoint is complete before it's actually complete. I've worked around this lag by embedding delays (e.g., 30 seconds) in a flow between actions like creating a table and getting the rows from that table.
Update: Re #2, here's another technique I just tried and seemed to work upon initial testing--loop until file/table access is confirmed.