.png){kind=logo}
Error with Contact List: Stopped at 50 Contacts, Support Needed
I was running a list for 600+ contacts, but it stopped at 50 and reported an error with instructions to contact support.
Mark L.··Hi Alex, could you let me know which table(s) you were working with? When you say "running a list", what precise actions were you taking? I want to make sure I'm looking in the right place.
Alex M.··this one: https://app.clay.com/workspaces/314703/tables/t_yii3uxk6tn8a/views/gv_48up8Vk9xsXh It stopped at fifty, but there should be lots more
- Mark L.··
Thank you! Looks like this is likely rooted in the 300+ exclusion keywords, which leads to extended processing time, and eventually times out. I notice a lot of redundancy in the "Exclude Description Keywords" list. There are many like "___ Borough Council", "___ City Council", and so on. (Or were those specifically chosen?) I recommend simplifying that by excluding the common root terms like "borough council", "city council", "town council", and "district council". I created a new table with a simplified list here: https://app.clay.com/workspaces/314703/tables/t_BVeetKFg6j7Y/views/gv_nduZmystGN6x The simplified keyword list is a wider exclusion, so results in fewer people, but the 484 were added there within a few moments. Does that help?
- Alex M.··
That is great. Thanks! Could you run the extended list?
- Mark L.··
I re-ran your original list minus one oddball term ("and other local government bodies: Camden London Borough"), and got 625 rows. https://app.clay.com/workspaces/314703/tables/t_yii3uxk6tn8a/views/gv_48up8Vk9xsXh I'd like some engineering perspective on the first runs, though, where we were only getting 50 back. I'll raise that internally in a moment, and share anything valuable I learn!
- Mark L.··
Alex, following up to confirm that the root issue here is related to volume of search terms. Reducing their number will help avoid query/timeout challenges like we saw in these tables. For the long run, I've got this on our engineers' radar to help improve error messaging for this. Thanks for raising it!
