A schedule that had been running successfully is now failing with a missing column error such as "Column doesn't exist", "Join columns in y must be present in the data.", "INVALID_FIELD", etc

Issues
#1

If a previously working schedule starts failing with a missing column error like one of the following;

  • “Column doesn’t exist,”
  • “Join columns in y must be present in the data.”
  • “INVALID_FIELD: (Column name)”

it may be due to changes in the source data. The cause and solution vary based on the type of data source.

  • Database as the data source: The column definition might have been altered by the database administrator. In this case, reach out to the administrator to confirm the column settings, update your content, and republish it.
  • Google Sheets or remote files as the data source: This issue may result from recent column name changes, sometimes made accidentally. Check the data source and correct any column name discrepancies.