GeezerVison

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 11, 2026 1:33am

PR Summary

Medium Risk
Changes the hot path for workflow cell persistence during execution; scope is limited to treating deleted rows as skips and typed errors, with tests covering skip vs throw behavior.

Overview
Workflow and enrichment cell writes now gracefully skip when the target row was deleted instead of failing or racing execution-status foreign keys.

A new TableRowNotFoundError replaces generic “row not found” throws from updateRow (and related row mutations). writeWorkflowGroupState catches that error on data patches and returns skipped without SSE events. Status-only execution updates first lock and verify the row (SELECT … FOR KEY SHARE) before writeExecutionsPatch; a missing row also yields skipped.

Unexpected write failures (e.g. database errors) still propagate; only missing-row cases are treated as benign.

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

Greptile Summary

The PR safely handles rows deleted while workflow or enrichment cells are executing.

• Adds a typed missing-row error for row updates and skips only that expected failure in cell writes.
• Locks the parent row during status-only execution writes so deletion and foreign-key cascades cannot race execution-state updates.
• Adds targeted coverage for deletion before pickup, deletion during a data write, and propagation of unrelated failures.

Confidence Score: 5/5

The PR appears safe to merge; the deletion race is handled without suppressing unrelated write failures.

The parent-row lock closes the execution-status foreign-key race, while the typed error catch narrowly handles rows disappearing from data-write paths and preserves unexpected exceptions.

sequenceDiagram
  participant Writer as Cell execution writer
  participant Rows as userTableRows
  participant Exec as tableRowExecutions
  participant Delete as Concurrent row deletion

  alt Data patch
    Writer->>Rows: updateRow(...)
    Rows-->>Writer: TableRowNotFoundError if deleted
    Writer-->>Writer: Return skipped
  else Status-only patch
    Writer->>Rows: SELECT ... FOR KEY SHARE
    alt Row exists
      Writer->>Exec: writeExecutionsPatch(...)
      Exec-->>Writer: Result
      Writer->>Rows: Commit and release lock
      Delete->>Rows: Delete row after lock release
    else Row missing
      Rows-->>Writer: No row
      Writer-->>Writer: Return skipped
    end
  end

_{Reviews (1): Last reviewed commit: "fix(tables): handle row deletion during ..." | Re-trigger Greptile}