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
Hari Kumar 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
We have a row limit of 11, and are only running a column on those 11 rows, but we're noticing it's actually running on all rows and we're seeing a spike in openai usage. Can someone please review this and see if it's an issue?
.png){kind=logo}
