Petra H.

It was a mix of some columns already there and some columns added after. This is definitely a bug because it just happened again for me. I was working in the table and only triggered it to run for 100 rows and it kept running for the entire list! Even after clicking multiple times on Stop Updates, it kept running and consuming credits. I'm on a call but will share a loom. Definitely need a credit refund here for the client

No changes to the table dependencies made at all. This is the first time we run into this issue, and I noticed this issue on 2 different workspaces. This never happened before I'm so certain so there must be something that changed

No there are 5k+ rows, as you can see in the screenshot. I just have a 10 row limit

Hari K. So when we run a column on 10 rows, it's supposed to run for 10 rows only. What we're noticing is that it's running for the entire column without us triggering it. I'd like to understand why that is happening, because it never used to happen before

Yeah we have run conditions, but we also have a limit and we're only run for those 11 rows. Can you please loop someone in? This is urgent

We have that already

https://app.clay.com/workspaces/689535/workbooks/wb_0t31dvwqx8sf6UwJzxH/tables/t_0t31xomxMPTsFCJ8XZg/views/gv_0t31xon2cGAdhRhWMzt