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

Issue with Uneditable Required Fields Preventing Re-Run | Clay

Issue with Uneditable Required Fields Preventing Re-Run

·Aug 08, 2025 12:13 AM·

Any idea why it's not letting me re-run with these "Required" fields filled in already and uneditable?

3 comments

· Sorted by Oldest

Clay
APP
·
·
When required fields are filled but uneditable and preventing re-runs, this typically indicates the enrichment is waiting for its inputs or has dependency issues. Try these solutions: Option 1: Click on the cell showing the issue and select "re-run this cell" Option 2: Right-click the column and use "Run All Rows that haven't run or have errors" Option 3: Toggle auto-update off and on again, then accept the run prompt The "Required to Run" toggle in enrichments ensures they only run when specific fields contain data, but sometimes dependency conflicts can cause this behavior.
Sources: Referencing dynamic data from other columns | Documentation | Clay University Run Options
Hunain F.
·
·
Hey, Jared G. You're facing an issue where required fields "View" and "Domain" are marked as required, but appear to be already filled in and yet uneditable, preventing you from re-running the signal in Clay. This is a common UX friction in Clay when something in the underlying table or configuration has changed. Here's the actual working solution to fix it: Click the ... next to "Company table" Re-select "Good fit ICP" manually. Select the "View" again after step 1 (it will become clickable). In "Domain" dropdown, manually pick the column with LinkedIn URLs or company domains.
Clay
APP
·
·
When required fields appear filled but uneditable, preventing signal re-runs, try clearing your browser cache and refreshing the view to resolve the issue. You can also perform a hard refresh using Cmd + Shift + R (Mac Chrome/Firefox) or Ctrl + F5 (PC). The "Required to Run" toggle in enrichments ensures they only run when specific fields contain data, but dependency conflicts can sometimes cause this behavior. Are you experiencing this issue with a specific signal type or enrichment column?
Source: Referencing dynamic data from other columns | Documentation | Clay University