The "Lookup Single Row in Other Table" feature is designed to be faster than multiple row lookups, but if it's spinning for minutes, there might be an issue. Here are some steps to try:
1. Check your table size and complexity. Large tables or complex queries may take longer to process.
2. Verify your inputs: ensure the Table to Search, Target Column, Filter Operator, and Row Value are correctly set.
3. Try using the Force Run option in the table settings. This may help refresh the data and resolve processing issues.
If the problem persists, you may want to request human assistance for a more in-depth investigation of your specific setup.
Anyone from Clay care to chime in on these issues?
All the responses to the bug reports have been bots or other people complaining about the same bug.
What is the process for getting clarity/resolution on the bugs?
Hey there Ted thanks for reaching out, sorry for the delay, this was related to an ongoing issue we were experiencing with loading in Clay. For your particular table this error cause the Lookup to be stuck in Queued. I have gone ahead and fixed this by first stopping the run and then while filtering for all the "Queued" rows in that Lookup column I have "Force Run: all of the rows to fix this.
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 02 Support.
Lookup Single Row in Other Table just spinning for minutes. | Clay
.png){kind=logo}
