Daniela D.

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.

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.

Happy to help! We'll keep you updated. We also have a status page up here: https://status.clay.com/

Hey there! We’re aware of an issue affecting AI and HTTP API templates where selecting them causes the table to crash. Our engineering team is actively working on a fix. We’ll keep you updated as soon as this is resolved. Truly sorry for the inconvenience.

Hey there! We’re aware of an issue affecting AI and HTTP API templates where selecting them causes the table to crash. Our engineering team is actively working on a fix. We’ll keep you updated as soon as this is resolved. Truly sorry for the inconvenience.

Hey Brendan! Sharing a quick video guide that covers identifying duplicates with the Lookup row integration: https://www.loom.com/share/a39a4569d95244b7886026f3c70812c7 Let me know if this helps.

Hey Denver! Thanks for the reply. Happy to clarify. The previous table is referencing this field (see screenshot below). The urls in that column don't match the required format. "Standardized LinkedIn URL (2)" is a duplicate of the correct column (used to test the signal). You can delete this and use the original column to recreate the search. Let me know if this helps!

Hey Denver! Thanks for reaching out. Happy to help. The job change signal used the wrong LinkedIn url format. We updated this in a new table and pulled the correct result (row 5): https://app.clay.com/workspaces/271513/workbooks/wb_0t5k5imxWtF7xkjm9Qp/tables/t_0t5khbnNkiZBGzM6Frn/views/gv_0t5khboBvMPvE4dhzyj Let me know if this helps!

Hey Denver! Thanks for reaching out. Happy to help. The job change signal used the wrong LinkedIn url format. We updated this in a new table and pulled the correct result (row 5): https://app.clay.com/workspaces/271513/workbooks/wb_0t5k5imxWtF7xkjm9Qp/tables/t_0t5khbnNkiZBGzM6Frn/views/gv_0t5khboBvMPvE4dhzyj Let me know if this helps!

Hey Himanshi! Sorry for the confusion. Happy to help. Could you share a screen recording of the values you're copying and pasting into your table? If you can share a sample size list, that'll help us troubleshoot this properly.