Concerns Over New Filter Limits Impacting Workflows

·

saw this filter limit got added today -- bit of a bummer and quite limiting for our workflows (maybe we're the only ones using lots of filters?). Is there a major performance / back end reason for why you guys had to add this?

4 comments

Channeled
APP
·
·
I couldn’t find specific information related to your question about the filter limit. Could you please rephrase or provide more details? I’m here to help!
Max T.
·
·
just feedback on a new update that I wanted to share
Channeled
APP
·
·
Based on the information available, filter limits appear to be implemented for performance reasons. Filter groups in Clay can be layered up to two levels deep to create advanced filtering conditions. This limitation likely helps maintain system performance. For specific features like finding people per company, there are options to set either a total limit on search results or a limit on results per company. Each search source has a maximum number of results that can be pulled into a table. Similar to how Google Sheets integrations have rate limits (300 read requests per minute) to prevent API overload, filter limits likely help manage system resources and ensure consistent performance for all users.
Source: Customize your table view | Documentation | Clay University
LuisArturo
·
·
Hey there Max thanks for reaching out, sorry for the delay here this limit was included for performance issues within tables as the number of filter start to cause some issues, this is something the team is looking into however.