Hello Team, I have a 50K row table and I was running my PredictLeads API.... to find the technology associated with each domain. After table finished running... it used all 100K Credits I had for the PredictLeads. It should suppose to use 50K only but it used double. Why is that? Anyone know the reason? The table used all my Predictleads credits. Any help or info would really appriciated.
I did talked with them and they shared the API Credit usage and it says we use 100K credits but I'm 100% confident that I do not run column twice. only once with 50K table.
I did not use another 50K table before. That was my first time using PredictLeads API for All Accounts A-L & All Accounts M-Z
So it's 26K + 23K = 49K but it used all 100K credits.
Nop. I haven't. This is the first time I used API.
Yes.. it's making two api calls for two different columns but how it used 100K credits when I run total 50K rows(combining both account list tables)
No Natalie. Here's thing: there is approx. 25K rows in one table and 25K rows in another table so it should consume only 25K credits per table right? But it consume 50K credits per table, how? Remember: both tables have different data, it's not same. I appreciate it if you help me understand where the issue is?
Yes... you calculation is right but there is one column of PredictLeads per table. and if you see majority of API calls are from "technology detection" API endpoint so if clay is not calling API endpoint twice, this should not happened in the first place.
Yes. bdw where can I submit the feature request. It would be really helpful, if clay started provided Audit Logs for users + force cancel when someone by mistake run all rows in the table.
Please do so.
Nop. We've got only above screenshot I shared with you.
This is no use Natalie.... how will I know it will not consume double credits next time? or how can I make sure it do not happen again? I follow everything perfect and still 50K credits go in thin air.
I already did Natalie... but I'm more concerned about 50K credits that got wasted. This is why I suggested below two features in first place.
It would be really helpful, if clay started provided Audit Logs for users + force cancel when someone by mistake run all rows in the table.