Troubleshooting 504 Gateway Time-out Error in Lookup Multiple Rows

On my column for Lookup Multiple Rows in Other Table, I got this error message. Why did this happen?

<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
</body>
</html>

11 comments

Channeled
APP
·
·
A "504 Gateway Time-out" error when using the "Lookup Multiple Rows in Other Table" feature typically occurs when the operation takes too long to complete. This can happen if you're trying to look up a large number of rows or if the table you're searching in is very large. To resolve this, try the following: 1. Reduce the number of rows you're looking up at once. 2. Use the optional "Limit" parameter to restrict the number of returned rows. 3. If possible, optimize your search criteria to narrow down the results. If the issue persists, you may need to break your lookup into smaller batches. If you need further assistance, please request human support by clicking on "Talk to a person" in this chat.
Sources: Lookup Multiple Rows in Other Table with Clay Lookup Rows | Documentation | Clay University Lookup Rows | Documentation | Clay University
Justin T.
·
·
There's onyl 13 rows in that table.
Channeled
APP
·
·
Even with only 13 rows, a "504 Gateway Time-out" error can occur due to various factors. Here are some possible reasons: 1. Complex search criteria or filter operations 2. Large number of columns in the target table 3. Server-side processing issues To resolve this, try: 1. Using the optional "Limit" parameter to restrict returned rows 2. Simplifying your search criteria 3. Reducing the number of columns you're retrieving If the issue persists, it might be a temporary server problem. Try again later or request human assistance by clicking on "Talk to a person" in this chat for further troubleshooting.
Sources: Lookup Rows | Documentation | Clay University Lookup Rows | Documentation | Clay University
Justin T.
·
·
theres only 10 clumns
Channeled
APP
·
·
Even with a small table, a "504 Gateway Time-out" error can occur due to various factors beyond just the number of rows and columns. This error suggests that the operation is taking longer than expected to complete. Here are some possible reasons and solutions: 1. Complex search criteria or filter operations 2. Server-side processing issues 3. Temporary network problems To resolve this, try: 1. Using the optional "Limit" parameter to restrict the number of returned rows 2. Simplifying your search criteria 3. Retrying the operation after a short wait If the issue persists, it might be a temporary server problem. In that case, please request human assistance by clicking on "Talk to a person" in this chat for further troubleshooting.
Sources: Lookup Rows | Documentation | Clay University Lookup Rows | Documentation | Clay University
LuisArturo
·
·
Hey there Justin thanks for reaching out, do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Justin T.
·
·
https://app.clay.com/workspaces/460716/workbooks/wb_FKteE6KFJPNX/tables/t_fExvykyZHZzE/views/gv_CMWuMVs2FSfM
Justin T.
·
·
tab Enrichment, row Final UserId
Justin T.
·
·
Ive resolved it since then, only happened once so far
LuisArturo
·
·
Great to hear that will check to see for future instances.
Channeled
APP
·
·