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
Learn Clay here
Clay Cup

Powered by Tightknit

Understanding Row Limit Impact on Action Execution | Clay

Understanding Row Limit Impact on Action Execution

·Jun 09, 2025 12:00 AM·

Hey! If I set the "Row limit" to 50 in the second field and then run an action on any column, will it apply only to those 50 rows in the current view, or will it run across all rows in the table?

Loading attachments

4 comments

· Sorted by Oldest

Channeled
APP
·
·
When you set a row limit of 50, this only affects what's displayed in your current view. If you run an action on a column, it will still apply to all rows in your table, not just the 50 visible rows. To run an action on specific rows only, you need to use the run options. You can: 1. Run starting from a specific row 2. Choose the number of rows to run 3. Run only rows with certain conditions These options are available when you right-click on a column.
Sources: Run Options Customize your table view | Documentation | Clay University Customize your table view | Documentation | Clay University
Nicolas F.
·
·
Is not working in that way
Nicolas F.
·
·
I just tried 3 times
Bo (.
·
·
Hey — setting the “Row limit” to 50 only affects the visible view. But if you make a change that triggers a dependent column (like editing a value), it can still run across all rows, even the hidden ones. Let me know if you’d like help setting up run conditions to control this.