Hey support team, for some our table stopped pulling in people switching roles - even though the schedule is setup correctly and on. https://app.clay.com/workspaces/17077/workbooks/wb_0svhgzuYKkstfr65NTo/tables/t_0swi5wyqkq5GbQyjseG/views/gv_0swi5x0Yxy234uxuBhc We have this over several different Clay tables. It worked in the beginning and just stopped pulling in new people (daily sync). Please help out - major issue .
Try a hard refresh first: Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac). Check if auto-update is enabled by clicking your Table name in the top bar, then select Enable auto-update from the dropdown if it's disabled. For job change monitoring, verify your setup: Go to Actions → Monitor for job changes, ensure your table has LinkedIn URLs, and confirm the schedule frequency is set correctly. If the issue persists across multiple tables after these steps, request human assistance by clicking Talk to a person.
Sources: Monitor for job changes | Documentation | Clay University Monitor for job changes | Documentation | Clay University Monitor for promotions | Documentation | Clay University Monitor for promotions | Documentation | Clay University FAQ: What are the default sync settings for CRM integrations? Salesforce | Documentation | Clay University
See here, not pulling in new people - even tho the schedule is on and it was working perfectly in the beginning.
In hindsight, all of them stopped running and not working anymore.
The only thing that works is scheduled pulling in open jobs
Hey Ruben V. it is when scheduled syncs suddenly stop working If your schedule is active and it was previously working, there are a few things we can check: 1. Filters or conditions sometimes changes in your filter logic or input data can silently block new results 2. Linked block issues if you're using a LinkedIn search block or similar, check if the underlying inputs (like role titles or companies) are still producing fresh results 3. Rate limits or API caps depending on the source, hitting rate limits might silently fail without clear error messages 4. Deduplication setting make sure the "Skip previously seen people" option isn’t filtering out new matches due to cached data I’d suggest duplicating the table and removing any filters to test raw output