Issue with Column Running and Credit Deduction in Slack

Bartosz Matuszkiewicz · 2024-12-10 09:50:08.964196+00

Hello. I've ran a column, credits were deducted but column was stucked on queue without actually running. I'm able to run individual cells, but it took credits again - so it look like I've spend around 2.5k credits without column ever running through - could someone take a look at this?

Issue with Column Running and Credit Deduction in Slack | Clay

11 comments

· Sorted by Oldest

Channeled
APP
·
·
Different providers have different charging policies for queries, which may explain the credit deductions you're experiencing. Some providers will charge credits just for attempting to find a result, regardless of whether the search is successful or not.To avoid unnecessary credit usage, I recommend: 1. Test with a small sample first (about 10 rows) to check if everything is working correctly before running the full column. 2. If you need to re-run specific cells, use the "Run all rows that haven't run or have errors" option to avoid duplicate charges on already successful searches.You can check which actions are refundable for each provider in our documentation to better understand when credits will be charged or refunded. Source: Guide: Ways to Save Clay Credits - Clay University
Bartosz Matuszkiewicz
·
·
It's not the case of lack of results, it looks like Clay got all cells stuck on queue
Channeled
APP
·
·
There are several ways to get your queued cells running: 1. For a quick test, try running just the first 10 columns by clicking "Save" > "Run First 10 Columns". 2. To run specific rows: • Right-click the column • Select "Run Column" and choose how many rows to run • Specify your starting row 3. If you need to run all pending rows, right-click the column and select "Run All Rows that haven't run or have errors". 4. For a complete refresh, you can force run all rows by right-clicking the column and selecting "Run Column" > "Force Run All Rows".If you continue experiencing issues, please email us at support@clay.com. Source: Run Options
Bartosz Matuszkiewicz
·
·
It's still not helpful, could someone look into this please?
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!
LuisArturo (Clay)
·
·
Hey there Bart thanks for reaching out, happy to take a look for you, do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1733859000&signature=22d0b37f9ad0d914e4b257215f26b6c5346bc91c8234b44703b189697ea58893&req=dSEgF85%2FmohWX%2FMW1HO4zYTywSj0A54W2BKsam%2FhVPs%2Bcg%3D%3D%0A
Bartosz Matuszkiewicz
·
·
sure - https://app.clay.com/workspaces/26665/workbooks/wb_ESqsUgoWGuBX/tables/t_ZAKwdUuB6ttD/views/gv_6hYaAQbmrMuM however you might want to see some logs, as I painstakingly ran them one by one, because I need this data today.
Arturo (Clay)
·
·
Hey Bart, thanks for following up. I ran a check and noticed so far the AI column consumed just under 13k credits but I've added them back into the account. I force ran the column so the issue where they remain stuck is corrected, basically like a hard refresh. It will only charge the credits once the call is finalized though, not if it happens to remain stuck for any reason (let me know if you run into that issue again though). Here's an example of the steps I took to force run the column: https://downloads.intercomcdn.com/i/o/w28k1kwz/1291861982/4feeccf9575a6c06c79d63edc5c0/CleanShot+2024-12-10+at+15_41_05%402x.png?expires=1733865300&signature=38eb7ba3c20bf84ec1a7c19ee90efd87fee013d28d4aaa0461bb95b4d671fde5&req=dSIuF8F4nIhXW%2FMW1HO4zfzR4XJ%2BDcFMhf%2BT31fOfhzJQJafHK5PMkXcOFu%2F%0AO3pJ%0A
Bartosz Matuszkiewicz
·
·
thanks Arturo, much appreciated! also force run feature seems useful, I wish I knew it earlier 🙂
Arturo (Clay)
·
·
No problem, thank you for surfacing this! This might've been related to a hiccup in the server in the past few days which was addressed but the requests that were in progress likely were affected. This should keep it going though! :D
Channeled
APP
·
·
Hi Bartosz Matuszkiewicz! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
Different providers have different charging policies for queries, which may explain the credit deductions you're experiencing. Some providers will charge credits just for attempting to find a result, regardless of whether the search is successful or not.To avoid unnecessary credit usage, I recommend: 1. Test with a small sample first (about 10 rows) to check if everything is working correctly before running the full column. 2. If you need to re-run specific cells, use the "Run all rows that haven't run or have errors" option to avoid duplicate charges on already successful searches.You can check which actions are refundable for each provider in our documentation to better understand when credits will be charged or refunded. Source: Guide: Ways to Save Clay Credits - Clay University
Bartosz Matuszkiewicz
·
·
It's not the case of lack of results, it looks like Clay got all cells stuck on queue
Channeled
APP
·
·
There are several ways to get your queued cells running: 1. For a quick test, try running just the first 10 columns by clicking "Save" > "Run First 10 Columns". 2. To run specific rows: • Right-click the column • Select "Run Column" and choose how many rows to run • Specify your starting row 3. If you need to run all pending rows, right-click the column and select "Run All Rows that haven't run or have errors". 4. For a complete refresh, you can force run all rows by right-clicking the column and selecting "Run Column" > "Force Run All Rows".If you continue experiencing issues, please email us at support@clay.com. Source: Run Options
Bartosz Matuszkiewicz
·
·
It's still not helpful, could someone look into this please?
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!
LuisArturo (Clay)
·
·
Hey there Bart thanks for reaching out, happy to take a look for you, do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1733859000&signature=22d0b37f9ad0d914e4b257215f26b6c5346bc91c8234b44703b189697ea58893&req=dSEgF85%2FmohWX%2FMW1HO4zYTywSj0A54W2BKsam%2FhVPs%2Bcg%3D%3D%0A
Bartosz Matuszkiewicz
·
·
sure - https://app.clay.com/workspaces/26665/workbooks/wb_ESqsUgoWGuBX/tables/t_ZAKwdUuB6ttD/views/gv_6hYaAQbmrMuM however you might want to see some logs, as I painstakingly ran them one by one, because I need this data today.
Arturo (Clay)
·
·
Hey Bart, thanks for following up. I ran a check and noticed so far the AI column consumed just under 13k credits but I've added them back into the account. I force ran the column so the issue where they remain stuck is corrected, basically like a hard refresh. It will only charge the credits once the call is finalized though, not if it happens to remain stuck for any reason (let me know if you run into that issue again though). Here's an example of the steps I took to force run the column: https://downloads.intercomcdn.com/i/o/w28k1kwz/1291861982/4feeccf9575a6c06c79d63edc5c0/CleanShot+2024-12-10+at+15_41_05%402x.png?expires=1733865300&signature=38eb7ba3c20bf84ec1a7c19ee90efd87fee013d28d4aaa0461bb95b4d671fde5&req=dSIuF8F4nIhXW%2FMW1HO4zfzR4XJ%2BDcFMhf%2BT31fOfhzJQJafHK5PMkXcOFu%2F%0AO3pJ%0A
Bartosz Matuszkiewicz
·
·
thanks Arturo, much appreciated! also force run feature seems useful, I wish I knew it earlier 🙂
Arturo (Clay)
·
·
No problem, thank you for surfacing this! This might've been related to a hiccup in the server in the past few days which was addressed but the requests that were in progress likely were affected. This should keep it going though! :D
Channeled
APP
·
·
Hi Bartosz Matuszkiewicz! This thread was recently closed by our Support team. If you have a moment, please share your feedback: