Unexpected parquet exception occurred. Class: 'ParquetStatusException'

Hi Toby,

this is exactly what I found out yesterday. (Drop the tables in Lakehouse / Warehouse) and rerun the dataflow solves the report for again only the 1st refresh.
But This is clearly a bug IMO. Replacing a table shouldt break the lineage (table names and so on didnt change..).
Maybe for now we could try something like this:
1.  using pipeline to schedule the DFs

2. adding a step (for warehouses it can be a stored procedure) before running the DF, which says - not drop the table - but delete all rows in the table

3. changing the DF from replace to append

maybe this works but clearly this should be a top issue to solve for the fabric team..