Understanding Error Messages When Credits Are Available

Harvey Le (C17 Labs) · 2025-03-16 13:47:28.926275+00

what does this error mean? Still have credits

Understanding Error Messages When Credits Are Available | Clay

6 comments

· Sorted by Oldest

Channeled
APP
·
·
The error you're seeing might be due to a temporary issue rather than a lack of credits. Here are a few steps you can try to resolve it: 1. Clear your browser cache and refresh the view. 2. If the error persists, try logging out of Clay and logging back in. This can help refresh your session token. 3. If you recently renewed your plan, it may take 1-2 hours for new credits to appear in your account due to transaction processing. If these steps don't resolve the issue, you may need to request human assistance for further troubleshooting.
Source: Running Out of Credits
Channeled
APP
·
·
Thanks for reaching out! Here is the full error message for what you're experiencing:
(43 kB)
(21 kB)
LBKSError code 400: {"error": true, "message": "INVALID_DOMAIN_NAME", "details": null}LBKSThe Prospeo documentation elaborates a little further: LBKS"The domain name you submitted is not reachable or does not have valid MX records."LBKSThis indicates that the domain in question isn’t reachable or doesn’t have valid MX (Mail Exchange) records. Essentially, this means that the domain either is not reachable (a few URLs are dead and don't actually go anywhere)or aren't set up to receive emails. Let us take row 13 in the table as an example. moderntimesgraphics.com isn’t set up to receive emails. I confirmed this by running a DNS lookup, and the domain doesn’t return any valid MX records, which aligns with what Prospeo states in their documentation. I've attached a couple of screenshots to show you what I mean. The first is with Clay.com and responds with an expected output, the second is with moderntimesgraphics.com and doesn't garner a response. If you're encountering this issue with multiple domains, it could be worth double-checking that the URLs in the Normalized URL column are correct and active. I hope that helps! Let me know if you have any further questions.
Harvey Le (C17 Labs)
·
·
Bo (Clay) is this true?
Bo (Clay)
·
·
Hey Harvey – Yup, we’re basically getting the errors from the backend that are being returned by the providers. Great response from Munnawar!
Harvey Le (C17 Labs)
·
·
I didn't see Munnawar, just clay ahah. thanks team
Channeled
APP
·
·

Channeled
APP
·
·
The error you're seeing might be due to a temporary issue rather than a lack of credits. Here are a few steps you can try to resolve it: 1. Clear your browser cache and refresh the view. 2. If the error persists, try logging out of Clay and logging back in. This can help refresh your session token. 3. If you recently renewed your plan, it may take 1-2 hours for new credits to appear in your account due to transaction processing. If these steps don't resolve the issue, you may need to request human assistance for further troubleshooting.
Source: Running Out of Credits
Channeled
APP
·
·
Thanks for reaching out! Here is the full error message for what you're experiencing:
(43 kB)
(21 kB)
LBKSError code 400: {"error": true, "message": "INVALID_DOMAIN_NAME", "details": null}LBKSThe Prospeo documentation elaborates a little further: LBKS"The domain name you submitted is not reachable or does not have valid MX records."LBKSThis indicates that the domain in question isn’t reachable or doesn’t have valid MX (Mail Exchange) records. Essentially, this means that the domain either is not reachable (a few URLs are dead and don't actually go anywhere)or aren't set up to receive emails. Let us take row 13 in the table as an example. moderntimesgraphics.com isn’t set up to receive emails. I confirmed this by running a DNS lookup, and the domain doesn’t return any valid MX records, which aligns with what Prospeo states in their documentation. I've attached a couple of screenshots to show you what I mean. The first is with Clay.com and responds with an expected output, the second is with moderntimesgraphics.com and doesn't garner a response. If you're encountering this issue with multiple domains, it could be worth double-checking that the URLs in the Normalized URL column are correct and active. I hope that helps! Let me know if you have any further questions.
Harvey Le (C17 Labs)
·
·
Bo (Clay) is this true?
Bo (Clay)
·
·
Hey Harvey – Yup, we’re basically getting the errors from the backend that are being returned by the providers. Great response from Munnawar!
Harvey Le (C17 Labs)
·
·
I didn't see Munnawar, just clay ahah. thanks team
Channeled
APP
·
·