Troubleshooting Clay Table Errors and Email Integration Issues

Md J. · 2024-09-18 08:36:07.229332+00

Hi team, Can you please help me figure out why I'm having a lot of errors in this Clay table in the column named "Octave Generate Emails"? Aslo, I have had issues with finding work email with the integration to Icypeas. I'm also having trouble merging columns. (please see the 3rd screenshot)

Troubleshooting Clay Table Errors and Email Integration Issues | Clay

14 comments

· Sorted by Oldest

Channeled
APP
·
·
💤 You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!
Bo (.
·
·
Hey, thanks for reaching out! 😊 1. Error: Timeout: This means we waited for a response but didn’t get one in time, so we stopped waiting. 2. Provider Procedure: We have to wait for the provider’s response. These calls take longer than standard API calls (like the ones you’re running), so we listen for a longer period. 3. Merge Issue (Stale Data): This happens when you’re working with stale or outdated data. To fix it, you need to re-run the columns that contain the stale data. Here’s an example of stale data explained. You can refresh the data by turning your table off and on again and accepting the charges. Here’s a video explaining this concept. Let me know if you need more help! 😊 https://downloads.intercomcdn.com/i/o/1185058528/ac06ce9758f61070dbc69d3a/CleanShot+2024-09-19+at+_15fwqATBBM%402x.png?expires=1726706700&signature=5fbdd7a654fbc779f3cc4256d3a46319c1a10e0d1da651f2df9cca3b50c67eda&req=dSEvE8l7lYRdUfMW1HO4ze96R7%2F%2BpO7aBIiUeLh%2FYRnzCh3WQ8f%2B2U6kAef9%0AnfsJ%0A
Md J.
·
·
Pranam L. Menelik A. Mentioning you to see if you can see messages here.
Menelik A.
·
·
Md J. Seen
1
Bruno R.
·
·
Hey there, thanks for reaching out. Were you able to look through the materials that Bo sent your way? If yes, is there anything else we can help you with here?
Md J.
·
·
Hi Bruno R., Yes, I went through the materials that Bo sent. Here’s what I understood from those materials regarding the merging column error: We use 7-8 Clay table templates to generate different copies. So, after duplicating the template, I’ll need to turn off the auto-update, and then load the contacts into the template. Before running anything, such as normalizing domains, finding emails, or running the copy API, I’ll need to turn auto-update back on. I expect this will resolve the merging column error, correct?
Md J.
·
·
Hello Bruno R. Bo (. I need your immediate assistance on this. We're experiencing an issue with the integration between Clay and Icypeas. Specifically, when trying to retrieve the work email, the system is showing "Awaiting callback..." instead of displaying the correct information. Could you please advise on how we can resolve this?
Loading attachments
Md J.
·
·
Bruno R. Bo (. I just saw an unknown credit charge in Clay for turning off the auto-update and then turning it back on again. I was working on this table: https://app.clay.com/workspaces/257306/tables/t_ZGFtEByD7h59/views/gv_zDvrwP5vkUX5
Tanvi R.
·
·
Hey there, you are correct! Turning on auto-update will address the stale data causing your merge column error. Let me know if you have any other questions! 😊
Arturo O.
·
·
Hey Jahid! Thanks for the follow up on this. I took a quick look and noticed you're using your own API key with Icypeas, and this appears to be a rate limit issue due to the number of request that are being processed. Given Icypeas works in a way that takes them a few minutes to process the request, they likely have a backlog to work through and are slow. It may be worth checking with them about your account to see how many pending requests they have directly on their system.
Md J.
·
·
Tanvi R. Bo (. Bruno R. I would like to understand how you charge for turning the auto-update on and off. Could you please provide some details on this? For example, are we being charged per row, cell, or in some other way? cc Pranam L.
Daniel K.
·
·
Hey Jahid! To manage your auto-update settings and prevent unintended credit depletion, you can turn off auto-update at the top of your table by selecting the three-dot icon beside the table name, then select auto-update. This action itself does not cost credits. However, when auto-update is on, any updates that occur will use credits. To avoid unexpected credit usage, it's recommended to test enrichments on a few rows before updating the entire table. For more detailed information on which actions cost credits, you can visit the Clay Credits Calculator. Hope that helps! :)
1
Md J.
·
·
Thanks, Daniel K.!
Channeled
APP
·
·
Hi Md J.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
💤 You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!
Bo (.
·
·
Hey, thanks for reaching out! 😊 1. Error: Timeout: This means we waited for a response but didn’t get one in time, so we stopped waiting. 2. Provider Procedure: We have to wait for the provider’s response. These calls take longer than standard API calls (like the ones you’re running), so we listen for a longer period. 3. Merge Issue (Stale Data): This happens when you’re working with stale or outdated data. To fix it, you need to re-run the columns that contain the stale data. Here’s an example of stale data explained. You can refresh the data by turning your table off and on again and accepting the charges. Here’s a video explaining this concept. Let me know if you need more help! 😊 https://downloads.intercomcdn.com/i/o/1185058528/ac06ce9758f61070dbc69d3a/CleanShot+2024-09-19+at+_15fwqATBBM%402x.png?expires=1726706700&signature=5fbdd7a654fbc779f3cc4256d3a46319c1a10e0d1da651f2df9cca3b50c67eda&req=dSEvE8l7lYRdUfMW1HO4ze96R7%2F%2BpO7aBIiUeLh%2FYRnzCh3WQ8f%2B2U6kAef9%0AnfsJ%0A
Md J.
·
·
Pranam L. Menelik A. Mentioning you to see if you can see messages here.
Menelik A.
·
·
Md J. Seen
1
Bruno R.
·
·
Hey there, thanks for reaching out. Were you able to look through the materials that Bo sent your way? If yes, is there anything else we can help you with here?
Md J.
·
·
Hi Bruno R., Yes, I went through the materials that Bo sent. Here’s what I understood from those materials regarding the merging column error: We use 7-8 Clay table templates to generate different copies. So, after duplicating the template, I’ll need to turn off the auto-update, and then load the contacts into the template. Before running anything, such as normalizing domains, finding emails, or running the copy API, I’ll need to turn auto-update back on. I expect this will resolve the merging column error, correct?
Md J.
·
·
Hello Bruno R. Bo (. I need your immediate assistance on this. We're experiencing an issue with the integration between Clay and Icypeas. Specifically, when trying to retrieve the work email, the system is showing "Awaiting callback..." instead of displaying the correct information. Could you please advise on how we can resolve this?
Loading attachments
Md J.
·
·
Bruno R. Bo (. I just saw an unknown credit charge in Clay for turning off the auto-update and then turning it back on again. I was working on this table: https://app.clay.com/workspaces/257306/tables/t_ZGFtEByD7h59/views/gv_zDvrwP5vkUX5
Tanvi R.
·
·
Hey there, you are correct! Turning on auto-update will address the stale data causing your merge column error. Let me know if you have any other questions! 😊
Arturo O.
·
·
Hey Jahid! Thanks for the follow up on this. I took a quick look and noticed you're using your own API key with Icypeas, and this appears to be a rate limit issue due to the number of request that are being processed. Given Icypeas works in a way that takes them a few minutes to process the request, they likely have a backlog to work through and are slow. It may be worth checking with them about your account to see how many pending requests they have directly on their system.
Md J.
·
·
Tanvi R. Bo (. Bruno R. I would like to understand how you charge for turning the auto-update on and off. Could you please provide some details on this? For example, are we being charged per row, cell, or in some other way? cc Pranam L.
Daniel K.
·
·
Hey Jahid! To manage your auto-update settings and prevent unintended credit depletion, you can turn off auto-update at the top of your table by selecting the three-dot icon beside the table name, then select auto-update. This action itself does not cost credits. However, when auto-update is on, any updates that occur will use credits. To avoid unexpected credit usage, it's recommended to test enrichments on a few rows before updating the entire table. For more detailed information on which actions cost credits, you can visit the Clay Credits Calculator. Hope that helps! :)
1
Md J.
·
·
Thanks, Daniel K.!
Channeled
APP
·
·
Hi Md J.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: