Issue with Clay Credits During Mobile Phone Search Process

Stephen S. · 2024-12-08 04:52:44.569173+00

Hello, I just upgraded and bought extra credits, but this mobile phone waterfall is telling me that I don't have enough clay credits. I think it is because it ate through all of the credits before confirming that it found a mobile phone (i.e., I am assuming that if it finished the process that there would be a substantial refund.) I have 2708 rows (~2100 qualified) for which I am trying to find a mobile phone for. How can I have this run through the whole process so that I can get the refunds? It estimated 25,000 credits before running, but it just burned through all of my credits (over 50K). Thank you!

Issue with Clay Credits During Mobile Phone Search Process | Clay

13 comments

· Sorted by Oldest

Channeled
APP
·
·
To complete the mobile phone waterfall process and handle the credit situation: 1. First, you'll need to purchase additional credits to continue the process. 2. Once you have more credits, you can restart the waterfall by: • Going to your first waterfall column • Using the "Run all rows that haven't run or have errors" option • This will only process the entries that weren't completed due to the credit shortage, avoiding duplicate runs on already successful searches.Regarding refunds: Waterfalls are designed to only charge you credits for the provider that successfully finds the data. You won't be charged for most actions that don't return a result. You can check the complete list of refundable actions in our documentation. Sources: Waterfall Providers Do Not Return Valid Data
Channeled
APP
·
·
Was our previous response helpful?
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Stephen S.
·
·
It charged me for all these redundant columns, unfortunately. I just bought even more credits, but it doesn't seem right since the waterfall promised to return successful mobile and to only pay for the one provider that delivered it.
Loading attachments
Stephen S.
·
·
It looks like perhaps the issue was that the ClearoutPhone validation had errors. But now I have spent a ton of credits on hitting the "Run all rows that haven't run or have errors" button on the phone data columns, and I was charged more than I should have been. What I should have done is hit that button on the validation column so that it restarted the waterfall from where it left off. I believe that the clearout phone errors were due to an api limit that was hit, so I switched to clay credits. Any help you might be able to offer in terms of a credit refund would be appreciated. Thank you
Daniela D.
·
·
Hey Stephen! Thanks for reaching out. Sorry about this. I’ve gone ahead and added those credits back to your workspace this time. It seems the providers continued to run because Clearout returned an error, which caused numbers not to be added to the final results column as they hadn’t been validated yet. If this happens again, the run should be restarted from the column that hasn’t finished updating—in this case, the first Clearout column that returned an error. If changes have been made to the waterfall configuration, it's best to filter your table based on the rows that returned an error from the first Clearout column and select the option to run the number of rows within that view. This will reset the logic and ensure providers update based on whether a valid mobile number is returned or not. It'll also help to prevent rows that were not affected from updating again. Let me know if this helps!
Stephen S.
·
·
Hi Daniela,
Stephen S.
·
·
Thank you for your help on this, and for adding back credits. This is helpful clarification to targe the first waterfall column with errors. I tried to restart with each column, but it wasn't working. So, filtering based on the errors makes sense, as there may be multiple errors staggered over different columns. Apparently the error was due to the clearout api, which limited the calls. They increased the calls to 250/minute, but I suppose that I should only do like 50 rows per run so that I don't hit the limitation?
Stephen S.
·
·
Or do you think I should ask for a higher api limit?
Bo (.
·
·
Asking for a higher limit is always the best here but if it's not possible, simply running in a limited way would also make sense :) https://downloads.intercomcdn.com/i/o/w28k1kwz/1289311666/60b005be6dcfcfa38974d47901d4/CleanShot+2024-12-09+at+_36XtChml8m%402x.png?expires=1733778000&signature=4663dbc907b49c5e48981b294df0a2e2b11a9ba9b91dd4a9fa820da22d721682&req=dSIvH8p%2FnIdZX%2FMW1HO4zXLocsZQNrmQCtltB5WZhceW2nCZRCix9x3sQlBf%0Aj04n%0A
1
Stephen S.
·
·
Hello, I am trying to use a fuzzy match to match to my salesforce records in another table. Is there a way to do this?
Mark L.
·
·
Stephen, what datapoints would you like to use for matching? The existing "Lookup Single Row..." enrichment would be the best starting point, but sounds more strict than you want.
1
Channeled
APP
·
·
Hi Stephen S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
To complete the mobile phone waterfall process and handle the credit situation: 1. First, you'll need to purchase additional credits to continue the process. 2. Once you have more credits, you can restart the waterfall by: • Going to your first waterfall column • Using the "Run all rows that haven't run or have errors" option • This will only process the entries that weren't completed due to the credit shortage, avoiding duplicate runs on already successful searches.Regarding refunds: Waterfalls are designed to only charge you credits for the provider that successfully finds the data. You won't be charged for most actions that don't return a result. You can check the complete list of refundable actions in our documentation. Sources: Waterfall Providers Do Not Return Valid Data
Channeled
APP
·
·
Was our previous response helpful?
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Stephen S.
·
·
It charged me for all these redundant columns, unfortunately. I just bought even more credits, but it doesn't seem right since the waterfall promised to return successful mobile and to only pay for the one provider that delivered it.
Loading attachments
Stephen S.
·
·
It looks like perhaps the issue was that the ClearoutPhone validation had errors. But now I have spent a ton of credits on hitting the "Run all rows that haven't run or have errors" button on the phone data columns, and I was charged more than I should have been. What I should have done is hit that button on the validation column so that it restarted the waterfall from where it left off. I believe that the clearout phone errors were due to an api limit that was hit, so I switched to clay credits. Any help you might be able to offer in terms of a credit refund would be appreciated. Thank you
Daniela D.
·
·
Hey Stephen! Thanks for reaching out. Sorry about this. I’ve gone ahead and added those credits back to your workspace this time. It seems the providers continued to run because Clearout returned an error, which caused numbers not to be added to the final results column as they hadn’t been validated yet. If this happens again, the run should be restarted from the column that hasn’t finished updating—in this case, the first Clearout column that returned an error. If changes have been made to the waterfall configuration, it's best to filter your table based on the rows that returned an error from the first Clearout column and select the option to run the number of rows within that view. This will reset the logic and ensure providers update based on whether a valid mobile number is returned or not. It'll also help to prevent rows that were not affected from updating again. Let me know if this helps!
Stephen S.
·
·
Hi Daniela,
Stephen S.
·
·
Thank you for your help on this, and for adding back credits. This is helpful clarification to targe the first waterfall column with errors. I tried to restart with each column, but it wasn't working. So, filtering based on the errors makes sense, as there may be multiple errors staggered over different columns. Apparently the error was due to the clearout api, which limited the calls. They increased the calls to 250/minute, but I suppose that I should only do like 50 rows per run so that I don't hit the limitation?
Stephen S.
·
·
Or do you think I should ask for a higher api limit?
Bo (.
·
·
Asking for a higher limit is always the best here but if it's not possible, simply running in a limited way would also make sense :) https://downloads.intercomcdn.com/i/o/w28k1kwz/1289311666/60b005be6dcfcfa38974d47901d4/CleanShot+2024-12-09+at+_36XtChml8m%402x.png?expires=1733778000&signature=4663dbc907b49c5e48981b294df0a2e2b11a9ba9b91dd4a9fa820da22d721682&req=dSIvH8p%2FnIdZX%2FMW1HO4zXLocsZQNrmQCtltB5WZhceW2nCZRCix9x3sQlBf%0Aj04n%0A
1
Stephen S.
·
·
Hello, I am trying to use a fuzzy match to match to my salesforce records in another table. Is there a way to do this?
Mark L.
·
·
Stephen, what datapoints would you like to use for matching? The existing "Lookup Single Row..." enrichment would be the best starting point, but sounds more strict than you want.
1
Channeled
APP
·
·
Hi Stephen S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: