Airtable support suggested that the cause may be a field which was created prior to 2023-03. That was not true in my case, as I created the field a few weeks ago. Instead, I believe the cause was a sync configuration which was created prior to 2023-0...