Issue with Broken Single Row Function Values

Olivier T. · 2025-04-16 08:03:23.777428+00

Lookup single row function is broken (again) as it says the values are wrong but they aren't

Issue with Broken Single Row Function Values | Clay

7 comments

· Sorted by Oldest

Channeled
APP
·
·
The Lookup Single Row function in Clay is designed to search and retrieve data from other tables in your workspace. It's possible that the error you're experiencing might be due to a mismatch in the input parameters or data types. To troubleshoot this issue, we recommend double-checking the following: 1. Ensure the "Table to Search" is correctly specified. 2. Verify that the "Target Column" exists in the selected table. 3. Check if the "Filter Operator" is appropriate for your data type. 4. Confirm that the "Row Value" matches the expected format in the target column. Can you provide more details about the specific values you're using for these parameters in your Lookup Single Row action?
Sources: Lookup Rows | Documentation | Clay University Lookup Single Row in Other Table with Clay
Stefano
·
·
Hey - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Olivier T.
·
·
I'ts multiple tables and this is the error: {"type":"BadRequest","message":"Invalid filter value 96183426 for field f_4ATgWwKMHBRH","details":null} BUT THAT'S NOT TRUE, cause the value is correct and it works for some rows and then stops working. Table here.
Bo (.
·
·
Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Bo (.
·
·
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?
Channeled
APP
·
·
LuisArturo
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.

Channeled
APP
·
·
The Lookup Single Row function in Clay is designed to search and retrieve data from other tables in your workspace. It's possible that the error you're experiencing might be due to a mismatch in the input parameters or data types. To troubleshoot this issue, we recommend double-checking the following: 1. Ensure the "Table to Search" is correctly specified. 2. Verify that the "Target Column" exists in the selected table. 3. Check if the "Filter Operator" is appropriate for your data type. 4. Confirm that the "Row Value" matches the expected format in the target column. Can you provide more details about the specific values you're using for these parameters in your Lookup Single Row action?
Sources: Lookup Rows | Documentation | Clay University Lookup Single Row in Other Table with Clay
Stefano
·
·
Hey - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Olivier T.
·
·
I'ts multiple tables and this is the error: {"type":"BadRequest","message":"Invalid filter value 96183426 for field f_4ATgWwKMHBRH","details":null} BUT THAT'S NOT TRUE, cause the value is correct and it works for some rows and then stops working. Table here.
Bo (.
·
·
Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Bo (.
·
·
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?
Channeled
APP
·
·
LuisArturo
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.