Hi support, how do we prevent this error?

Hey Joessa, thanks for reaching out! Could you share the table where this is occurring so we can take a closer look? Also are you using your own API key or Clay credits for this enrichment?

Hey Joessa, thanks for reaching out! Could you share the URL to the table where this is occurring so we can take a closer look? Also are you using your own API key or Clay credits for this enrichment?

Hi Owen. We're using our own API key. Here's the table: https://app.clay.com/workspaces/285280/tables/t_P3rtztUNQHdN/views/gv_b7otA9b2za8Y

Hey, thanks for reaching out Joessa, while our team answer back I wanted to provide more infos. Typically our integrations are designed to fit their own API limits, but if you run multiple different integrations at multiple different place then it consume your limits. So the only way to prevent this is not to run multiple different variations of that integration since it'll throw this error. You can also try to reach out to them and ask to increase their rate limits, some providers are more lenient than others but i'm not sure for them :)

Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.

We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!