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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 15, 2026 4:46am

PR Summary

Medium Risk
Mostly copy/label changes, but the cancel endpoint now performs a direct DB update on running logs which could affect cancellation state consistency if the conditional update is wrong or races with executor finalization.

Overview
Terminology update: Replaces user-facing references to workflow “executions” with “runs” across docs, UI labels/menus, error strings, emails, and log search suggestions (e.g., “Cancel Run”, “Run ID”, “Run failed/cancelled”, “Run logs persisted”).

Cancellation behavior: Updates POST /api/workflows/[id]/executions/[executionId]/cancel to directly set the workflowExecutionLogs row from running → cancelled (with endedAt) when cancellation is durably recorded or locally aborted, preventing the UI from briefly reverting to running; adds targeted tests for the new DB-update paths and failure tolerance.

^{Reviewed by Cursor Bugbot for commit 3454745. Configure here.}

Greptile Summary

This PR renames user-facing "execution" terminology to "run" across the app UI, emails, search suggestions, and docs, and adds an optimistic DB status update in the cancel API route so the UI reflects cancelled immediately without waiting for the executor to finalize.

Two missed renames remain in the user-facing string surface: search-suggestions.ts getMatchingTriggers still emits \"${label}-triggered executions\" while its sibling getFilterValues was already updated, and workflow-execution-utils.ts line 655 still uses 'Workflow execution failed' as a fallback error shown in the console panel.

Confidence Score: 5/5

Safe to merge; all remaining findings are minor P2 copy inconsistencies with no runtime impact.

The functional change (optimistic DB cancel update) is well-guarded with a WHERE clause, a try/catch, and solid test coverage. The rename sweep is thorough with only two P2 copy misses found. No logic, security, or data-integrity issues.

apps/sim/lib/logs/search-suggestions.ts (line 607) and apps/sim/app/workspace/[workspaceId]/w/[workflowId]/utils/workflow-execution-utils.ts (line 655) have leftover "execution" copy.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant UI
    participant CancelAPI as Cancel API Route
    participant Redis as Redis (markExecutionCancelled)
    participant DB as Database
    participant Executor

    UI->>CancelAPI: POST /cancel
    CancelAPI->>Redis: markExecutionCancelled(executionId)
    Redis-->>CancelAPI: { durablyRecorded: true }
    CancelAPI->>DB: UPDATE SET status='cancelled' WHERE executionId=? AND status='running'
    DB-->>CancelAPI: OK (UI now sees 'cancelled' immediately)
    CancelAPI-->>UI: { success: true }
    Note over Executor: Still processing...
    Executor->>Redis: Reads cancellation flag
    Executor->>DB: Writes final 'cancelled' status

_{Reviews (1): Last reviewed commit: "fix(mothership): remove duplicate handle..." | Re-trigger Greptile}