nothing wrong with my filters

Try clearing your browser cache and refreshing the page - this often resolves persistent error messages like this.

If that doesn't work, the preview might be having trouble loading due to your filter combination. Even though your filters look fine, sometimes the preview can't process certain combinations properly. [1]

You could also try temporarily removing some filters to see if the preview loads, then add them back one by one to identify which combination is causing the issue.

Was that helpful?

no talk to human

Got it — I’m connecting you to a human teammate now.

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!

Hi Oliver, looking into it now 👌🏼

thanks Quentin R. - my team is also getting the same error on this table

Oliver, would you mind sharing the table URL you're working on?

Here's the table Quentin R. https://app.clay.com/workspaces/48037/workbooks/wb_0t8g267sjmK5S92Pxyv?sidebarAction=openCommandCenter

I made this video for a team member but it might be helpful as well: https://www.loom.com/share/376c5028d8e147eb955360ebca4cd980

Thanks for sharing the Loom video, super helpful on our end for reproducing the issue.

From what I can see, the key difference between this table and the ones that work is size. “Rec - UK (1–10k+) Industries” is significantly larger than the others, which points to a bug on our side. I’ve gone ahead and filed this with our engineers to investigate.

I did some additional testing as well. When I created a separate view (“Support View”) capped at ~20k rows, everything worked as expected. That said, having to run multiple searches or maintain separate views isn’t ideal.

One interesting workaround I found: instead of using Domain (Main) as the reference field, switching to company_linkedin_url made your original view work without any row limits.

Curious what you think. Does that workaround fit your use case for now while we dig into the root cause?