Post Upgrade to v1.39.1 - Airtable Node Output Fields BROKEN

[dkindlund]

Post Upgrade to v1.39.1 - Airtable Node Output Fields BROKEN

[Joffcom]

Hey @dkindlund,

This should be fixed in 1.41.0 can you try upgrading, The PR that fixes this issue can be found here: #9324

[dkindlund]

Thanks, @Joffcom -- do you happen to know if the devs added unit tests to explicitly check for this issue in the future? (Just trying to make sure there are no future regressions around this.)

[dkindlund]

Also, it looks like v1.41.0 is a pre-release -- any idea when it will become the latest release, @Joffcom ?

[dkindlund]

Lastly, @Joffcom , for any legacy workflows that I did not save since upgrading to 1.39.1 -- do you know if the older Output Fields that were saved in those legacy workflows will still be correctly restored after upgrading? Or, do I need to go back through each and every workflow using Airtable and manually fix this issue across all workflows?

[dkindlund]

Okay, @Joffcom , after upgrading to 1.41.0, I see the following:

• The underlying issue has been fixed.
• Legacy workflows that used Airtable that were not recently saved have their Output Fields restored.
• Any new or updated workflows that used Airtable and were recently saved post 1.39.1 had their Output Fields obliterated and you'll have to manually go back in and fix each and every Airtable-specific workflow.

[Joffcom]

Hey @dkindlund

Most of the time if we fix an issue we will add a test, Looking at the PR a test has been added to check for this in the future.

This issue only impacts newly created nodes or recently opened nodes that used that UI component. It was not an Airtable specific issue.

While 1.41.0 is marked as pre-release there have not been any bugs in it so far to suggest that it will get a .1 release before it becomes latest on Wednesday when we release 1.42.0 but that may change if anything came in last night.

It may also be worth thinking about a test environment if n8n is a core part of what you do just to give you an extra layer when you update to be confident that any critical workflows don't start to fail. While we don't set out to release bugs we do know that sometimes things can sneak through and it is always better to be safe with a test setup that you can manually run a couple of your own workflows to see if the issue occurs.

For now as this issue is already fixed though I am going to close this one. Let me know if you have any other questions on it.