Issue with Lookup Single Row Stuck in Queue Showing No Record Found

Aviv F. · 2025-07-29T16:59:21.245Z

What’s going on with the `Lookup single row` that is stuck on Queue and then shows `No record found` which isn’t accurate?

Issue with Lookup Single Row Stuck in Queue Showing No Record Found | Clay

9 comments

· Sorted by Oldest

Aviv F.
·
·
https://app.clay.com/workspaces/199281/tables/t_0t05azp6AcWueF7nopo/views/gv_RJHsh9bQ5raK
Clay
APP
·
·
If your lookup column is stuck on "queued," click the column header and select Force Rerun Column to reset it and get things moving. You can also try clicking on the column header, hovering over the Run column field in the dropdown, and selecting Force to jump start the run. This helps recover the cell state in case of performance issues and won't apply additional charges for re-running these rows.
Clay
APP
·
·
If your lookup column is stuck on "queued," click the column header and select Force Rerun Column to reset it. You can also click the column header, hover over Run column in the dropdown, and select Force to jump start the run. This helps recover the cell state and won't apply additional charges for re-running these rows. This should resolve both the queued status and the incorrect "No record found" result.
Aviv F.
·
·
The problem is with the returned results not with it being queued although that did start like that
Clay
APP
·
·
For incorrect "No record found" results in lookup single row, verify your lookup configuration: ** Table to Search: Ensure you're targeting the correct table ** Target Column: Confirm the column you're searching in contains the expected data ** Filter Operator: Check if you're using the right operator (equals, contains, etc.) ** Row Value: Verify the value you're searching for matches exactly what's in the target table The lookup single row action searches for exact matches based on your specified criteria, so mismatched formatting or incorrect column selection can cause legitimate records to appear as "not found."
Sources: Lookup Rows | Documentation | Clay University Lookup Single Row in Other Table with Clay Lookup Rows | Documentation | Clay University
Aviv F.
·
·
https://app.clay.com/workspaces/199281/tables/t_0t05azp6AcWueF7nopo/views/gv_RJHsh9bQ5raK
Aviv F.
·
·
apologies please ignore all good here
Luca P.
·
·
Hey Aviv, just checking in! How did things go? Let me know if theres anything else I can do here to assist. :)
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in Clay Support.

Aviv F.
·
·
https://app.clay.com/workspaces/199281/tables/t_0t05azp6AcWueF7nopo/views/gv_RJHsh9bQ5raK
Clay
APP
·
·
If your lookup column is stuck on "queued," click the column header and select Force Rerun Column to reset it and get things moving. You can also try clicking on the column header, hovering over the Run column field in the dropdown, and selecting Force to jump start the run. This helps recover the cell state in case of performance issues and won't apply additional charges for re-running these rows.
Clay
APP
·
·
If your lookup column is stuck on "queued," click the column header and select Force Rerun Column to reset it. You can also click the column header, hover over Run column in the dropdown, and select Force to jump start the run. This helps recover the cell state and won't apply additional charges for re-running these rows. This should resolve both the queued status and the incorrect "No record found" result.
Aviv F.
·
·
The problem is with the returned results not with it being queued although that did start like that
Clay
APP
·
·
For incorrect "No record found" results in lookup single row, verify your lookup configuration: ** Table to Search: Ensure you're targeting the correct table ** Target Column: Confirm the column you're searching in contains the expected data ** Filter Operator: Check if you're using the right operator (equals, contains, etc.) ** Row Value: Verify the value you're searching for matches exactly what's in the target table The lookup single row action searches for exact matches based on your specified criteria, so mismatched formatting or incorrect column selection can cause legitimate records to appear as "not found."
Sources: Lookup Rows | Documentation | Clay University Lookup Single Row in Other Table with Clay Lookup Rows | Documentation | Clay University
Aviv F.
·
·
https://app.clay.com/workspaces/199281/tables/t_0t05azp6AcWueF7nopo/views/gv_RJHsh9bQ5raK
Aviv F.
·
·
apologies please ignore all good here
Luca P.
·
·
Hey Aviv, just checking in! How did things go? Let me know if theres anything else I can do here to assist. :)
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in Clay Support.