Issues with Run Condition Not Met in Zenrows LinkedIn Scrape

Petar R. · 2025-10-30T17:47:22.432Z

I use "cell status" formula for Zenrows linkedin scrape enrichment as a condition for employee size qualification. It works fine when auto-update is turned off in zenrows enrichment, because my condition is: output check if linkedin scrape status is not unknown. The part that sucks is when I turn on auto-update or the column all of a sudden I have "Run condition not met" on all 16000 records, even if I don't run anything before that. My whole table is turned off. Why is this happening???

Issues with Run Condition Not Met in Zenrows LinkedIn Scrape | Clay

Clay Support
APP
·
·
When you enable auto-update on your Zenrows enrichment, it resets the column status for all rows, causing them to show "UNKNOWN" status initially. Your conditional formula checking for "not unknown" then fails, triggering "Run condition not met" across all 16,000 records.
To fix this, use a status/flag column approach to prevent infinite loops. Create a formula column using Clay.getCellStatus({{zenrows_field_id}}) to check if the Zenrows column has completed processing, then use this in your "only run if" condition instead of checking the status directly. [1]
This ensures your dependent columns only execute after the Zenrows scrape finishes—even if it returns no data—preventing the auto-update reset issue.
Clay Support
APP
·
·
Was that helpful?
Clay Support
APP
·
·
If you still need help resolving the auto-update issue with your Zenrows enrichment, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other challenges you’re facing?
Petar R.
·
·
I don't understand, could you explain this logic as I'm 15yo? This is what happens before the company size qualifier:
Find the linkedin url with claygent then output it in Company Linkedin column. Fallback is NO (in case it doesn't find it).
Scrape the company linkedin column with Zenrows.
Use formula to extract number of employees.
We disqualify companies that have less then 50 employees. We also consider they have less then 50 if Claygent can't find their linkedin url - so we qualify those as well. I need my qualification to be real-time. Only when all columns have finished their runs. Can you help me create a formula for that?
Clay Support
APP
·
·
Think of it like a production line where each step must finish before the next one starts.
Create a status checker formula using:
Clay.getCellStatus({{claygent_field_id}}) == "completed" AND Clay.getCellStatus({{zenrows_field_id}}) == "completed"
Then in your company size qualifier's "Only run if" condition, reference this status checker column.
This ensures your qualifier only runs after both Claygent (LinkedIn URL finder) AND Zenrows (scraper) are completely done—preventing the "Run condition not met" issue when auto-update resets everything. [1]
Your qualifier will then check: if employees < 50 OR LinkedIn URL = "NO", disqualify the company. [2]
Clay Support
APP
·
·
Did that answer your question?
Petar R.
·
·
what will happen if run conditions not met on Linkedin SCrape?
Clay Support
APP
·
·
If run conditions aren't met on your LinkedIn Scrape column, it will show "Run condition not met" and skip execution entirely.
This means:
No scraping attempt occurs
The cell remains empty or shows the "Run condition not met" message
Any downstream columns depending on this data will also fail their conditions
Your employee size qualifier won't have scrape data to evaluate
To fix this, ensure your LinkedIn Scrape column's "Only run if" condition accounts for when the LinkedIn URL exists (not "NO" from Claygent). [1] Use a condition like: {{Company Linkedin Url}} != "NO" so it only scrapes when Claygent found a valid URL.
Clay Support
APP
·
·
Did that answer your question?
Petar R.
·
·
yes, that makes sense. that's exactly what I have now. But as soon as I turn on auto-update for both columns I will have run conditions not met by default on all zernrows because linkedin url column will be empty because I didn't run it yet! then my company qualifier column will be checked.
Petar R.
·
·
will be checked, sorry
Clay Support
APP
·
·
You're hitting the classic auto-update timing issue! When auto-update is enabled, all columns try to run simultaneously on empty rows, causing the dependency chain to break.
Solution: Create a master status checker formula column:
Clay.getCellStatus({{claygent_linkedin_url_field_id}}) == "completed" AND Clay.getCellStatus({{zenrows_scrape_field_id}}) == "completed"
Then use this status checker in your company qualifier's "Only run if" condition instead of checking the data directly.
This prevents the qualifier from running until both upstream columns finish—even when auto-update starts with empty cells. The status checker waits for completion rather than checking data values, solving your timing problem. [1]
Clay Support
APP
·
·
Did that answer your question?
Petar R.
·
·
I created this formula for zenrows only. It's showing false even for successful scrapes, why?
Loading attachments
Clay Support
APP
·
·
The Clay.getCellStatus() function returns different values than what you see in the UI. When a scrape shows "Scrape Successful," the actual status returned by getCellStatus() is likely "successful" not "completed."
Try changing your formula to:
Clay.getCellStatus({{Linkedin Scrape 2}}).toLowerCase() === "successful"
The status values returned by getCellStatus() include "successful," "running," and "failed" - not "completed." [1] You can click into a specific cell to see the exact status details if needed.

20 comments