This appears to be a limitation of the Excel Online/Graph API connector rather than an issue with your flow.
The List rows present in a table action relies on Excel Online through Microsoft Graph. If the workbook contains unsupported features, such as a digital signature line or signed workbook content, the connector may fail with errors like 502 Bad Gateway or unsupported features in this workbook.
A few options you can consider:
Use an unsigned processing copy
Keep the original signed/signature-line workbook for the business process.
Create a copy without the signature line.
Have Power Automate read from the unsigned copy.
Move the data to a separate Excel table
Keep the signature document separate.
Store the actual rows/data in a normal Excel table without the signature feature.
Let the flow read that file instead.
Use SharePoint or Dataverse instead of Excel for the data
If the process is business-critical, Excel with signatures may not be the best backend for automation.
A SharePoint list or Dataverse table will be much more reliable for Power Automate.
Use Power Automate Desktop as a workaround
If you must interact with the signed/signature-line Excel file, desktop automation may be able to open Excel directly and extract the data.
This is more fragile than cloud flow actions, but may work when the cloud Excel connector cannot.
In short, the Excel connector does not handle all Excel workbook features. Since the error specifically says unsupported workbook features, I would avoid using the signed/signature-line workbook directly in the cloud flow and instead automate against a clean copy or a separate data source.