I literally just got bit with this regression, documented here:
Impact:
50+ workflows broken
Airtable node logic broken
Can’t downgrade, because a recent v1.62.x DB migration breaks the DB for older versions of n8n
It’s frustrating because:
I certainly like new features/functionality that’s added to n8n
But, these sorts of regressions make upgrading exceptionally painful
I highly recommend snapshotting your n8n DB BEFORE upgrading, just in case this happens to you.
I also wish there were more Airtable-specific unit tests in n8n, to be honest. This bug appears within 1 min of upgrading most production workflows involving Airtable.
It is far from ideal but this bug likely impacts other nodes as well and is something that will be looked into on Monday morning.
For anyone upgrading I would always recommend 2 steps…
Back up the database, this will allow you to restore an older version if there is a database change.
Update a test environment first and run a couple of workflows to make sure everything works as expected
While we don’t set out to release a new version with bugs it does sometimes happen and we often implement tests to prevent it from happening again. Over the last year we have spent a lot of time working on improving our test coverage and while it isn’t fully there yet it is a lot better than it was.