Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Clay Cup

Powered by Tightknit

Rerunning Scheduled Column Processes: Full vs Partial Execution? | Clay

Rerunning Scheduled Column Processes: Full vs Partial Execution?

·Jul 08, 2025 02:52 PM·

does rerunning columns on a schedule within a table force rerun the entire column or just reruns rows that can be rerun due to errors, timeouts, etc?

3 comments

· Sorted by Oldest

Clay
APP
·
·
Scheduled columns automatically re-run specific columns or entire tables on a recurring basis to keep your data current without manual updates. The scheduling feature lets you automatically run your workflows at the cadence you set - daily, weekly, or monthly. However, the documentation doesn't specify whether scheduled runs force rerun the entire column or only target rows with errors, timeouts, or other issues. The scheduling feature is described as keeping enrichment data up-to-date like company headcount, funding info, or tech stack changes, but the exact behavior regarding which rows get processed isn't detailed. Are you looking to schedule runs for a specific use case where you want to avoid reprocessing successful rows, or do you need all rows refreshed regularly?
Sources: Scheduled columns | Documentation | Clay University Scheduled columns | Documentation | Clay University Scheduled columns | Documentation | Clay University
Mike R.
·
·
Smit V.
·
·
Hi Mike, thank you for reaching out! When you set up columns to run on a schedule, all the rows would re-run and not just the ones that has errors or didn't run before. Let me know if I can help you with anything else :) - Smit