A query that worked last month can fail this month without anyone touching it, because the source changed. The error names what broke:
- Expression.Error: The column 'Customer' of the table wasn't found. The source renamed or removed a column that a step still names. Add a Table.RenameColumns step right after the source, so every later step and the report keep the old name. MissingField.Ignore lets the same step run on files that still use the old name.
- Files that disagree. October's file says Qty and November's says Units. Table.Combine lines columns up by name, so the combined table gets both, each half empty. Rename in each file before combining.
- DataFormat.Error: We couldn't convert to Number. A new value such as "n/a" reached a number column. Decide what it means: usually not known yet, so replace it with null before the type change. Removing the row hides an order from the report.
Fix the smallest thing that restores the result, and keep the output columns the report expects. The broken query shows its error when you open it.
One rename after the source fixes the failing step and keeps Customer for the steps and the report that use it.