Is the "Filter" broken? It has been a few days and filters are not exactly filtering...
The screenshot shows "No filters" is currently active, meaning no filters are applied to your table. [1]
To add a filter:
Click the Filter button at the top of your table
Click + Add filter
Select the column to filter
Choose a comparison operator (equal to, contains, etc.)
Enter your filter value
If you're still seeing empty rows after filtering, try clearing your browser cache and refreshing the screen—this can resolve front-end display issues.
Is that what you were looking for?
Even when I select a filter, it does not work as intended. This view has 3k rows, several not empty, but it gives me no results. This is also happening across multiple workspaces. That is why I am asking support.
I'm sorry to hear the filters aren't working as expected. I'll connect you to a human agent who can assist you further with this issue.
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!
Hi Gui - thanks so much for reaching out and for your patience here. I don't believe the filtering should be an issue, this seems to be working as expected. Could you please share a link to the table in which you're seeing this issue?
Here you go Aditi S. https://app.clay.com/workspaces/605608/workbooks/wb_0t33udf3KYCVYFtsEaa/tables/t_0t34734VBDgCewiKa3F/views/gv_0t347358WgEWXKYcYqZ Filter the column "Work Email (2)" = is not empty And Starting Row = 6000, Row Limit = 3000. Let me know what you see.
Thanks for sharing the table - taking a deeper look to see what's happening here.
Gui - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Yeah, I had this happen accross multiple workspaces that is why I raised the issue. I spent some time on this, if you want to give more context to the engineering team: If you use the "Starting Row/Row Limit" + the normal filter, it breaks. But if you don't use the Starting row, sometimes it works.
Appreciate the context Gui!
Hi Gui - just heard back from the engineering team. I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog.
For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change.
One thing they've mentioned here as a workaround is the following: you can filter for the row 6000-9000 first, add a text column that mark these rows in some way, then filter for that value as part of the filter. Hopefully that helps as a workaround. Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you.
For sure, no problem at all. I just wanted to bring this up to the team as I am aware of other Clay users having the same issue.
Really appreciate you flagging this for us Gui! As mentioned, we will let you know when progress has been made specifically on this.
🫶
