Issues with New Leads Not Running in Lemlist Campaign

Noah · 2025-10-21 07:34:07.644392+00

Hello there, I'm trying to push some newly added leads to my Lemlist campaign but seems like the new rows are not running correctly. I tried force run but then the new rows aren't even running , clicking them individually just causes an infinite loader, restarting my computer didn't work either, ... anyone experiencing the same?

Issues with New Leads Not Running in Lemlist Campaign | Clay

12 comments

· Sorted by Oldest

Clay Support
APP
·
·
Try these steps to resolve the infinite loading and stuck rows:
For stuck enrichments:
Click the column header of your Lemlist columns
Hover over "Run column field" in the dropdown
Select "Force" to jump start the column
For "Run condition not met" rows:
Click the "explain" button next to the message - AI will explain why the condition wasn't met
Review your run conditions to ensure they align with your data (e.g., required fields are populated)
If columns remain stuck:
Try a hard refresh: Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac)
Check if there are dependencies between columns causing issues
To prevent infinite loops:
Ensure your Lemlist integration isn't creating circular triggers
Use status columns to track processed rows
Set conditional runs to only trigger when specific conditions are met [1]
If these steps don't resolve the issue, request human assistance by clicking "Talk to a person."
Clay Support
APP
·
·
Was that helpful?
Asad R.
·
·
yes same issue here
1
Clay Support
APP
·
·
Since you're experiencing the same infinite loading issue, try these additional solutions:
For persistent stuck columns:
Perform a hard refresh: Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac)
Check for infinite loops:
Review if your Lemlist integration is creating circular triggers
Ensure the enrichment isn't updating fields that trigger itself
Add conditional logic to only run when specific conditions are met [1]
If columns remain stuck after force running:
Create a duplicate column and run it on empty rows
Filter for rows where the current column "is empty"
Use the merge columns feature to combine results
If these steps don't resolve the issue, request human assistance by clicking "Talk to a person."
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the issue with your Lemlist campaign rows, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific errors you’re encountering?
Noah
·
·
This did not help, I'd like to talk to a person
Clay Support
APP
·
·
I understand your frustration, and I’m routing you to a human agent who can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
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!
Loading attachments
Noah
·
·
https://app.clay.com/workspaces/314705/workbooks/wb_0t1p0jyGPQ9ApXgVDZN/tables/t_0t2dmsfUCT2a4ZXXzpu/views/gv_0t2dmsfHk3YFezx4auB
Kashif J.
·
·
Hi Noah, Thanks for reaching out! I reviewed your workbook and identified the issue with the columns "Add to Beperkte personalisatie Campaign (Rinata) (2)" and "Add to TS Campaign."
Both columns depend on the "Normalized Company Name Result" field as input. I noticed that many rows past row ~140 in this Claygent action column were stuck mid-execution and unable to produce outputs, which caused the downstream Lemlist actions to fail due to missing inputs.
To test this, I manually re-ran a few of the stuck Claygent tasks in the "Normalized Name" column. Once these completed successfully, the corresponding Lemlist actions also seemed to run without issues.
Recommended next steps: Re-run all the stuck Claygent actions in the "Normalized Company Name Result" column (this strange Claygent behavior may be a lingering effect from yesterday's AWS outage). Once those complete, your Lemlist columns should process normally. Let me know if this fixes your problem, or if you continue to experience any issues after trying this!
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!

Clay Support
APP
·
·
Try these steps to resolve the infinite loading and stuck rows:
For stuck enrichments:
Click the column header of your Lemlist columns
Hover over "Run column field" in the dropdown
Select "Force" to jump start the column
For "Run condition not met" rows:
Click the "explain" button next to the message - AI will explain why the condition wasn't met
Review your run conditions to ensure they align with your data (e.g., required fields are populated)
If columns remain stuck:
Try a hard refresh: Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac)
Check if there are dependencies between columns causing issues
To prevent infinite loops:
Ensure your Lemlist integration isn't creating circular triggers
Use status columns to track processed rows
Set conditional runs to only trigger when specific conditions are met [1]
If these steps don't resolve the issue, request human assistance by clicking "Talk to a person."
Clay Support
APP
·
·
Was that helpful?
Asad R.
·
·
yes same issue here
1
Clay Support
APP
·
·
Since you're experiencing the same infinite loading issue, try these additional solutions:
For persistent stuck columns:
Perform a hard refresh: Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac)
Check for infinite loops:
Review if your Lemlist integration is creating circular triggers
Ensure the enrichment isn't updating fields that trigger itself
Add conditional logic to only run when specific conditions are met [1]
If columns remain stuck after force running:
Create a duplicate column and run it on empty rows
Filter for rows where the current column "is empty"
Use the merge columns feature to combine results
If these steps don't resolve the issue, request human assistance by clicking "Talk to a person."
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the issue with your Lemlist campaign rows, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific errors you’re encountering?
Noah
·
·
This did not help, I'd like to talk to a person
Clay Support
APP
·
·
I understand your frustration, and I’m routing you to a human agent who can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
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!
Loading attachments
Noah
·
·
https://app.clay.com/workspaces/314705/workbooks/wb_0t1p0jyGPQ9ApXgVDZN/tables/t_0t2dmsfUCT2a4ZXXzpu/views/gv_0t2dmsfHk3YFezx4auB
Kashif J.
·
·
Hi Noah, Thanks for reaching out! I reviewed your workbook and identified the issue with the columns "Add to Beperkte personalisatie Campaign (Rinata) (2)" and "Add to TS Campaign."
Both columns depend on the "Normalized Company Name Result" field as input. I noticed that many rows past row ~140 in this Claygent action column were stuck mid-execution and unable to produce outputs, which caused the downstream Lemlist actions to fail due to missing inputs.
To test this, I manually re-ran a few of the stuck Claygent tasks in the "Normalized Name" column. Once these completed successfully, the corresponding Lemlist actions also seemed to run without issues.
Recommended next steps: Re-run all the stuck Claygent actions in the "Normalized Company Name Result" column (this strange Claygent behavior may be a lingering effect from yesterday's AWS outage). Once those complete, your Lemlist columns should process normally. Let me know if this fixes your problem, or if you continue to experience any issues after trying this!
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!