Max K.

thanks for the update Arturo! I have tested it and it looks like it's been resolved and working with those errors. Appreciate all the follow-up and here here 🙏

There are definitely a lot of them coming at the same time, but it seems like there's queueing from Clay side to ensure it's not submitting thousands of queries at once. From Snowflake's side, i dont' see any failures or issues (no queueing either) except for transaction blocking, which is expected since there are numerous queries trying to update the same table

Hi Arturo, I just force re-ran for all the rows in that table, and im still running into the Runtime Error unfortunately 😞. I can try it on a different table if you want me to, but it seems like it hasn't been fully resolved yet from my end

Got it. For reference, we don't actually need those synced at the moment. I was just using it to test out for this particular issue. We will have others soon that will require that we able to consistently run this automatically without having to retry manually, so would love an update on the issue when you get them!

Hi Arturo, I have just tried re-running the upsert for all the rows in that table, but are running into the same Runtime Error again unfortunately. I'm using the same table as the one I linked above

That's a great news! thanks for following up with me. lmk when it's released

Hi, i didn't create a Loom as it would not be useful for the most part as we wait for the cells to update and run into this issue, but I just re-ran it for the same table and I have left the cells with Runtime Error so that you can take a look. Feel free to re-run them if you need to on your end. Clay table with Runtime error (check the ❄️ Upsert Row): https://app.clay.com/workspaces/239721/tables/t_TxfcVu4dTJ8R/views/gv_sCFHV6NxQKex

Hi, is there an update to this by any chance? we are trying to automate some of our workflow and this may block us from doing so. Thank you!

Thanks Arturo! Will post back here if we run into it again. As an additional context, it happens when we try to sync over a lot of rows (thousands of rows)

Hey Daniela, yep i'm aware of the different errors that happen when it's due to the format and have addressed those before as those have an error message associated with them. But these ones we are encountering are Runtime error that has no error details and would succeed on a next retry without any changes. I don't think we have any table atm that still has those errored cells as we re-ran them until they were all successful, but we can probably re-run few of them if you need to see the actual error