The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 12, 2026 4:27am

PR Summary

Medium Risk
Changes when background workflow auto-runs are dispatched for table groups, which can affect unintended job execution. The fix is narrowly scoped and more conservative than the previous behavior.

Overview
Prevents unintended auto-run when updating legacy table groups that lack a persisted autoRun field.

updateTableGroupUseCase and updateWorkflowTableGroup now set startAutoRun only on an explicit false → true transition (previousGroup.autoRun === false), instead of treating any non-true prior value (including undefined) as a newly enabled toggle.

Adds regression tests covering both update paths for legacy enabled groups.

^{Reviewed by Cursor Bugbot for commit 6bd9537. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

The PR narrows table-group auto-run dispatch to explicit false-to-true transitions so saving legacy groups with no persisted autoRun value does not start execution.

• Updates both generic and workflow-specific group update commands.
• Adds regression tests for legacy groups whose autoRun property is absent.

Confidence Score: 4/5

The PR appears safe to merge, with only a non-blocking gap in coverage for explicitly enabling a disabled group.

The implementation consistently prevents legacy undefined-to-true saves from dispatching while retaining explicit false-to-true behavior, but the added tests exercise only the suppression side of that contract.

Files Needing Attention: apps/sim/lib/table/application/groups.test.ts

_{Reviews (1): Last reviewed commit: "fix(tables): prevent legacy group auto-r..." | Re-trigger Greptile}