This is happening in more than one base. When I Find a Record in an automation, when I try to select a field in script config or an email field, the Field ID returns instead of the name of the field. I’m not able to do any development until I can figure this out. Please help. thanks.

As a data point when I try to use the results from a ‘Find Record’ action and a single select field it looks like this for me:

I restored the base from a snapshot yesterday morning, and the field select process and the field select process is happening normally. I would appreciate a response from Airtable about what caused this system failure and how to prevent it from happening again. Thanks.

Well, the restored snapshot that was working is now generating the same bad behavior.

Here’s an update, though, I finally realized that even though it is returning the field ID instead of the field name, it is working and returning record values. That’s somewhat better, but makes the code hard to read. Again: any idea why this is happening?

Hey ​@mpalsf this is clearly a bug!!!
Not happening on my end.

Make sure to reach out to support@airtable.com to make sure they can take care of it.

Mike, Consultant @ Automatic Nation

We are experiencing this issue, as well.

Seems like the virus has spread lol. I’m experiencing the bug as well now.

​@mpalsf did you gen any answer form Airtable?

Mike, Consultant @ Automatic Nation

No. It’s weirdly not fatal, but makes the automations hard to read.

Thanks for the reply. I appreciate knowing it’s not just me.

Is there a way to get Airtable’s attention for a real bug?

I saw that Airtable behaviour in similar case, when trying to use array of values where the system expects a single string value. And I saw it before, maybe less than month ago, but more that week, but I didn’t care because it worked as I need - converted this array into a comma-separated list. The issue is only about a name of token in Automations UI, Field Name vs Field ID

I managed to get both results for similar Find records actions, It happens even in Update step
 

after some investigation I found that it happens when trigger table is different from Find Records table. But it doesn’t happen when a trigger has no table at all, like scheduled time.
 

So it can read Fieldnames only in table with Test1
Even when I changed the order of Find Records, it still uses same table

But when I removed step with Test1 and created again, it is now using Test2 for field names
Old token became invalid, new token now shows field ID. Test2 is OK.

 

So it seens like automation uses some exact table to translate Field ids to names and that table defined somehow. (by trigger, or if trigger is table-independent, by other actions during automation)

 

Wow, nice detective work. Hopefully this will help Airtable fix the issue.

i think i am experiencing the same or a related issue. i was trying to work on a conditional automation and when i try to click on the “edit conditions” to see what is happening with this long string of code, it errors out. 

I’ve tried testing this many ways, and it’s a bit of a blur. Try selecting that field again. I remember a problem initially, but now when I select the field, it returns the underlying field ID, but it also works.

the issue i was experienceing seems to have resolved overnight. i did not get any help from support, but the fields are now legible and i am able to edit my automations again. so that is good.