Bug Report: Workflow Fails on Bulk Execution for Email Address Lookup | Clay

Bug Report: Workflow Fails on Bulk Execution for Email Address Lookup | Clay

Clay Support
APP
·
·
This sounds like a workflow sequencing issue where bulk runs are causing timing conflicts between dependent columns.
The "run condition not met" during bulk execution typically happens when:
Column dependencies aren't properly configured
Auto-update settings create race conditions
Run conditions reference fields that change mid-execution
Quick fixes to try:
1.
Check your run conditions - Click the "explain" button on failed cells to see why conditions weren't met
2.
Use proper sequencing - In your email column's "Run Settings", add an "Only run if" condition that checks if prerequisite columns have completed
3.
Turn off table auto-update while testing - This prevents chain reactions during bulk runs [1]
4.
Use Clay.getCellStatus() formula - Create a formula column with Clay.getCellStatus(#{{field_id}}) to check if dependent columns finished before running email enrichment
Before diving deeper into troubleshooting, I'd recommend trying our built-in AI tool Sculptor (top-right corner) to help optimize your workflow setup. It can quickly identify sequencing issues and suggest fixes.
Let me know if Sculptor helps or if you need more specific guidance on the run conditions!
Clay Support
APP
·
·
Is that what you were looking for?
Jannis E.
·
·
1.
I don't see an insue here
2.
Should work
3.
Okay
4.
The dependent rows finished (I can see the results before)
Clay Support
APP
·
·
Got it - if the dependent columns are already finished and showing results, but you're still getting "run condition not met" during bulk runs, try this:
Click the "explain" button on any failed cells to see exactly why the condition wasn't met. Sometimes the issue isn't obvious from just looking at the data.
You can also try Force running the stuck cells:
- Click the column header
- Hover over "Run" in the dropdown
- Select "Force" to jump start them
If that doesn't help, I'd recommend trying Sculptor (top-right corner) - it can quickly analyze your workflow and identify what's causing the bulk run issues that single runs don't have.
Let me know what the "explain" button shows or if Sculptor helps identify the root cause!
Clay Support
APP
·
·
Did that answer your question?
Jannis E.
·
·
no
Clay Support
APP
·
·
Thanks for letting me know. I’m connecting you to a human agent who can assist you further with this issue.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.

If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Jannis E.
·
·
PS: Please ignore the rows 134+ as I already used them for other campaigns and don't want to rerun them
Natalie H.
·
·
Hi Jannis, thanks for reaching out. I spotted the issue and filmed a walkthrough explanation in my own test account here: https://www.loom.com/share/9d7868a66f9e49f89fedf5971246a317 Let me know if you have further questions.
Jannis E.
·
·
Thank you for getting back to me! Unfortunately it seems like that wasn't the issue. Here a 30 second video: https://www.tella.tv/video/troubleshooting-a-persistent-issue-1o3c
Bo (.
·
·
Hey,
What’s happening here is expected based on how run states work.
Your original column ran in an earlier state. After that, changes were made to the column and downstream steps, but the full chain was never re-run together. When you re-run rows now, Clay recalculates the entire dependency chain using the current configuration, not the old state.
Because of that, previous outputs like campaign values can get cleared or changed. That’s what you’re seeing in your video. It’s not a bug, it’s the table recomputing everything based on the latest logic.
The key thing to check is which run conditions or downstream actions changed after the original run. Follow the column flow downstream and look for conditions that would now evaluate differently when rows are re-run.
If you don’t want rows 134+ to be affected, don’t re-run those rows. Any re-run will force a full recalculation for that row.
Let me know if you have more questions.
Jannis E.
·
·
Hey Bo, first of all, happy new year! I hope you've had an amazing time with your loved ones! Secondly, I did added new companies and did a complete fresh run, but the issue still persists. Here the video: https://www.tella.tv/video/janniss-video-88mn
Bo (.
·
·
Hey,
From your walkthrough, the issue isn’t that things “aren’t running”, it’s that the inputs your run conditions depend on are still changing at the next steps.
You can confirm this quickly by clicking into a cell that shows Run condition not met. That view will tell you which condition failed and what value it evaluated at the time.
Even if the columns look like they ran, when you re-trigger them the relevance score and the upstream context fields can recalculate, and that means:
the run conditions can flip mid-run
the “15 rows” you think you’re targeting can change as the scoring updates
the downstream columns either don’t run when you expect, or they run against incomplete inputs and produce the wrong outputs
So the root cause is timing. The table needs a chance to fully finish calculating before you trigger the next batch.
Basically:
Value 1 comes in → returns a score → run conditions are checked
You re-trigger the rows → it changes the setup
Run conditions aren’t met anymore
Let me know if you have more questions.
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.

Still need help here? Reply back and someone will jump back in.

Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!