hey team, Clay table wont stop self-creating "filters" and Im unable to delete them. It keeps going up and down between 65-70 filters on its own. Here's the table: https://app.clay.com/workspaces/449716/workbooks/wb_0t45kwfnGsh5TiJguYS/tables/t_0t4iiw5Fo4EVW5nQjRm/views/gv_0t45s7x4ftzKBbUMmec
This sounds like you're experiencing an infinite loop where filters are continuously being created and removed automatically. [1]
Immediate fix:
Pause all automations in your table by turning off auto-update (click the table dropdown menu → "Disable auto-update") [2]
Stop any running enrichments using the "Stop Updates" button
Likely cause:
An enrichment column may be auto-running based on a field it's also updating, causing continuous re-runs that generate filters.
Next steps:
Check which columns have auto-update enabled and disable them temporarily
Look for enrichment columns that might be triggering based on their own output
If the issue persists after pausing automations, click "Talk to a person" for further assistance with diagnosing the loop pattern.
Is that what you were looking for?
No, need support. Potential bug
Sorry to hear you're having this issue. I’m routing you to our human team now so they can assist you further.
Clay Support is sharing a file with you.
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!
hey team, Clay table wont stop self-creating "filters" and Im unable to delete them. It keeps going up and down between 65-70 filters on its own. Here's the table: https://app.clay.com/workspaces/449716/workbooks/wb_0t45kwfnGsh5TiJguYS/tables/t_0t4iiw5Fo4EVW5nQjRm/views/gv_0t45s7x4ftzKBbUMmec
I can't completely understand - Could you please create a Loom video - what you actually want
im reporting a bug bro lol not much to do here
the table is self-creating filters on its own non-stop
Hi Andi - thanks so much for reaching out. Are you still facing this issue? This was a bug but was fixed recently by our team.
