The issue happens when you set the fields parameter and the trigger field is not included. So, to solve it, you can either not set it and return all fields or add the Updated Time Weight field to the fields parameter. In case you want to do the latter, It should look like this: Weight,Updated Time Weight - Make sure yo include the emoji.
This problem keeps coming back and I several times managed to make it work but didn’t know why.
Today I probably discovered the issue (or at least one of them).
It looks like the airtable trigger pulls the FIRST record created as an example, no matter which field was last modified. And as long as the “last modified time” of this first record (the one we use in automation) is not populated - it throws an error that this field doesn’t exist.
Have a look at this gif. It seems like a bug to me as we don’t always to have this record filled.
So temporary solution is to find out which record was created first (by using “created time” option) and make sure this field has been populated. Obviously the field related to this “last modified time” field can be deleted, as the deletion is a registered event and mod time field will remain populated