Thanks — that clarifies both auto-run spend and why Stop can appear to keep running.
We’ll open a ticket now with workspace/table/column + timestamps for the incident review.
Quick question: is there any way (or workaround) to add guardrails like a spend cap / confirmation prompt before an auto-run column dispatches at scale? We’re scaling high-volume workflows and want no surprises — happy to follow any recommended best-practice pattern for batching + run conditions to avoid accidental retriggers.
