Lookup Enrichment Triggering Issue Despite Auto Update Off

Petar R. · 2025-11-13T00:24:33.882Z

My lookup enrichment is triggering even when the auto update is turned off on the enrichment itself. Please look at this loom video: https://www.loom.com/share/522e73b6e3bd4e7c9b53041a4b728374 It's urgent please get back to me asap and let me know what's going on. Link to table: https://app.clay.com/workspaces/421655/workbooks/wb_0t5mfy66mpsTGDNuvYi/tables/t_0t5mfzr5prmNJWtzhKM/views/gv_0t5mfzruYD5eSQC79PC

Lookup Enrichment Triggering Issue Despite Auto Update Off | Clay

Clay Support
APP
·
·
Even with column auto-update disabled, enrichments can still trigger due to table-level auto-update settings or infinite loops. [1]
Check if table auto-update is enabled by clicking your table name and selecting "Disable auto-update" if needed. Table-level settings override column-level auto-update settings.
Also verify if your enrichment creates an infinite loop - this happens when an enrichment modifies the same field that triggers it, causing continuous re-runs. [2] To fix this, use conditional logic like "Only run if [processed field] is empty" or separate your trigger field from output fields.
If you need further help troubleshooting this specific table, just ask to speak to a human.
Clay Support
APP
·
·
Did that answer your question?
Petar R.
·
·
Table auto update is turned on. But the enrichment should not run if it's turned off. The workflow should be blocked there. Please connect me to a human agent. This is most likely a bug. This was not happening before
Clay Support
APP
·
·
I understand your concern and will connect you to a human agent who can assist further with this issue.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Petar R.
·
·
https://app.clay.com/workspaces/421655/workbooks/wb_0t5mfy66mpsTGDNuvYi/tables/t_0t5mfzr5prmNJWtzhKM/views/gv_0t5mfzruYD5eSQC79PC
Petar R.
·
·
Urgent- please
Mayato (.
·
·
Hi Petar, sorry for the experience it looks like 2768 records were affected. Unfortunately, we cannot undo the action if it's already performed. Did this action affect your data or any unintended credit usage?
Petar R.
·
·
Yes unfortunately, but not clay credits. Api calls. You can top up some credits if you want. But more importantly, let me know when the issue is ficed please so that I can launch our campaigns.
Petar R.
·
·
Thanks Mayato (.
Petar R.
·
·
hey Mayato (. any news on this???
Petar R.
·
·
I still have this issue. Can you give me the ETA on this please???? I need to know the ETA on fix so that I can plan the campaign launch. Thanks for understanding!
Mayato (.
·
·
Hi Peter, sorry, happy to take a look further. Could you please briefly describe the issue that you are still facing? I have looked at your table and the lookup records action in the last column seems working?
Petar R.
·
·
Hey Mayato (. i fixed it by removing the bad lookup column and creating new one. But I don't want to close the ticket. It happened already few times that I have a bug like this but the real issue was not fixed. I had it with checkbox formula not registering anything and with lookup. By the time we should dive deeper, I have already found the solution because I can't wait. Then the ticket closes. Can we see what caused this issue, so it won't happen again?
Sayli G.
·
·
Hello Petar! Thanks for reaching out! Jumping in for Mayato here. I did see another report of this but have not seen this to be a consistent issue. Have you seen this happen consistently? I don't think it should happen again. Let me take a look at the loom and see if there is any other approach we can take!

19 comments