Deep Matching - No results

Hey ​@Jeroen_Sarink,

I’m not experiencing this issue myself. It does take a VERY VERY long time to find the best match, even for tables of only two records. Having said that, it does work. Do you get a “no results found” or similar, or does it take forever searching?


If the issue persits I’d suggest you reach out to support@airtable.com and make sure to ask for a human answer. They are usually nice and helpful!

If it helps, I’d be happy to hop on a brief call w you and take a look at it. Feel free to grab a slot if you think that can help in any way.

Completely different matter, but would love to have you join our Airtable Hackathon! Make sure to sign up!!

Mike, Consultant @ Automatic Nation 
YouTube Channel

Lucky you ;)

This is all I'm getting: it starts with ´Generating...´ and after a long while (15 mins?) it changes to ‘Still pending: Queued for generation...’. Finally (after approx. 2 hours?), the process ends with a ‘Something went wrong...’ message.

Oh, I see. That seems to be Runtime error, right?  “Couldn’t generate within time limit…..”

Let me be super clear: My test was actually sing a two record table. Would you mind setting up a new view to show only one record for example, and give it a shot?

Under my test, it was taking a very long time with only 2 records. I can imagine how +100 record table would result in timeout (obviously a big issue).

I’ll test with bigger tables later today and keep you posted! For anybody not aware of what Deep Match is, you can read more about it here.

Completely different matter, but would love to have you join our Airtable Hackathon! Make sure to sign up!!

Mike, Consultant @ Automatic Nation 
YouTube Channel

I've done some more testing and it seems to be linked to the base in which the tables live.

Nearly empty test base

🟢 I've created two test tables with a deep match link between them and the links are generated after a few seconds.

Our regular base

🔴 I've recreated the exact same test tables, records and deep match settings, but without any results.

This base is quite heavily used, with approx. 300k records and a lot of ´real-time’ syncing going on through the API. We´re getting API timeouts on these syncs regularly (multiple each day), so I guess this base is pushing Airtable's performance limits. I assume this is the cause of the Deep Matching issue.

I'll get in touch with Airtable support about this.

Thanks for your help ​@Mike_AutomaticN!

Oh, really interesting debugging!!

Please do make sure to reach out to support though, I’d love to know their answer.

Completely different matter, but would love to have you join our Airtable Hackathon! Make sure to sign up!!

Mike, Consultant @ Automatic Nation 
YouTube Channel