Skip to main content

Hi

The Find Records action has a bug.

I have an automation when a new record is created, use the 'Find Records' action to find a record in another table and link them together. Very straightforward and works.

However if the new record created has empty fields for the conditions of the lookup, it returns ALL the records in the other table when it shouldn't return any records since an empty field does not equal to a non empty field.

In the screenshots you can see that the record selected to test automation has an empty email and phone number field.

But the Find Records actions returned all the records in the lookup table.

This is a bug and not the first time it has been raised as mentioned in this community post:
https://community.airtable.com/t5/automations/when-source-is-blank-automation-links-all-records-from-another/td-p/176602?utm_source=chatgpt.com

But the solution in that post doesn't work in my instance as I need to use the conditional actions for another process.

This seems like a simple fix from Airtable's side and is bug as the evaluation of empty == non-empty should be false except Airtable think it's true.

Maybe I misunderstand how this action works but why does Find Records return all the records in the other table when the trigger record has an empty field?

How can this bug get reported? 


@JayC wrote:

How can this bug get reported? 




You can use the in-app help to contact support and report the bug. Or you can email support@airtable.com. I recommend including a short video recording where you show all the configuration screens for the automation, the data view with values for the records, how you trigger the automation, and the resuts.



@JayC wrote:

How can this bug get reported? 




You can use the in-app help to contact support and report the bug. Or you can email support@airtable.com. I recommend including a short video recording where you show all the configuration screens for the automation, the data view with values for the records, how you trigger the automation, and the resuts.


I've already spoken to Airtable support but they are not recognising this as an issue and instead trying to just provide a workaround that doesn't work for my use case.

So trying to get more awareness of this bug.


Reply