Hi Aisyah •
This is a pretty common hiccup with Redshift Spectrum when the Parquet schema drifts. Basically, Spectrum external tables don’t auto‑refresh when new columns show up, so if the pipeline adds fields, your table definition gets out of sync. The fix is usually to run an ALTER TABLE … ADD COLUMN for each new field so the external table matches the Parquet schema again. If the changes are big or messy, sometimes it’s easier to just drop and recreate the external table with the updated schema pointing to the same location. Another trick: if you’re using Glue Data Catalog, you can update the schema there and Redshift will pick it up. After that, queries should stop throwing the Spectrum Scan Error.
If everything is okay, don't forget to share your experience with the issue by "Accept answer". If you need more information, feel free to leave a message. We are happy to help!