Hey so a list ran without my permission and continued even when I pressed pause multiple times. A few rows paused but it was 50,000 rows and ran all of our credits. I feel like that is an unfair situation. Can this be fixed? My client is pissed. Clay S.
We're sorry to hear about this issue. To prevent unintended auto-updates and credit depletion in the future: 1. Test enrichments on a few rows before updating the entire table. 2. Turn off auto-update at the top of your table by selecting the three-dot icon beside the table name, then select auto-update. 3. Use conditional runs and filtered views to optimize credit usage. For the current situation, you can purchase credit top-ups if you need more credits immediately. Go to Workspace Settings > Plans and Billing > Purchase Credits, select the amount needed, and click Continue. If you need further assistance or want to discuss the specific circumstances of this incident, please request human support by clicking on "Talk to a person".
Source: Running Out of Credits
It's been on manual the entire time
Hey there Jalen thanks for reaching out, do you mind sending the link (url) to the table so we can take a look?
Hey Jalen - I'm happy to add them back, but would love to help you avoid this issue in the future.
Got it. Stopping a run will still take a moment as shown in the warning messages, but this situation is totally understandable.
How many credits do you feel it shouldn't have run? Do you know how to prevent this from happening again?
Bo (. and the thing is that it looked like it stopped. I scrolled down the list and it said "Run Stopped" on a bunch of them and I looked at the credits and they weren't moving anymore. Then suddenly I get a message from my client saying we ran out of credits and I looked at the table again but scrolled down further on the list only to see it was still trying to run
This was more than an hour later that it was still trying to run
I stopped it at a little over 7000 (or atleast I tried to.
Hey Jalen, thanks for reaching out and for pointing this out to us. Is the link that you provided the table where this happened? (link) Regardless, stopping the updates can take a few minutes given the volume of API requests that are being made per second within a Clay table. However, in this case it looks like it took much longer than a few minutes. I'd love to take a closer look but it appears that this table was deleted. Did you end up deleting the table? Included a bit more context about how to stop/prevent Clay tables from running. :) --------context-------- When it comes to stopping or pausing an entire Clay table, you can do so in a few various ways: ** Table Level: Click the logo in the bottom-right corner of the screen and selecting 'Turn off Table'. This will prevent any rows from running automatically until the table is turned back on. (as shown in image one) ** Column Level: Alternatively, to pause updates at the column level, click the column header, go to the column settings, scroll to the bottom of the menu, and toggle off 'Auto-Update' in 'run settings' (as shown in image two) ** *Pausing Cells Mid-Run: If a column is already running you can click the 'Stop Updates' button to stop these enrichments from continuing as quickly as possible. (as shown in image three) Hope this helps! Let me know how else I can assist. :)
Also, Jalen. Just saw you're other thread as well, happy to provide a one-time refund for this. Could you just confirm which workspace these credits were spent in initially? Ideally, confirming the name and 6 digit number that is found in the URL as shown in the image below. Happy to help here!