PR Summary

Medium Risk
Changes enforce additional workflow validation in both deploy and run paths, which may newly reject previously deployable/runnable workflows if validation is overly strict or edge cases exist.

Overview
Deployment now enforces workflow integrity checks end-to-end. The deploy API (POST /api/workflows/[id]/deploy) now calls validateWorkflowState before schedule validation and returns a 400 with a combined error summary when blocks/edges/tool references are invalid.

UI now prevents invalid operations earlier. The deploy button runs runPreDeployChecks() even for already-deployed workflows before opening the redeploy modal, and the Run action (including the global shortcut) is disabled when a workflow has multiple blocks but no edges (disconnected graph).

^{Written by Cursor Bugbot for commit 2766a39. This will update automatically on new commits. Configure here.}

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 9, 2026 1:19am

Greptile Summary

This PR closes a meaningful security/UX gap by adding workflow state validation at three enforcement points: a backend validateWorkflowState() gate before deployment, front-end pre-deploy checks that now apply to redeployments as well as first deploys, and a live Run-button guard based on edge connectivity. The approach is sound and the backend change is clean, but the new Run-button heuristic has two issues that need attention before merge.

• Backend (deploy/route.ts): validateWorkflowState() is correctly placed before the schedule check and will catch unknown block types, dangling edge references, and bad tool references. The only minor concern is the as WorkflowState cast that omits the variables field.
• Frontend (use-deployment.ts): Moving the isDeployed short-circuit to after runPreDeployChecks is a clean, correct change with no issues.
• Frontend (panel.tsx): The hasBlocks && !hasEdges guard replaces the always-false placeholder, which is an improvement, but it is too broad — any workflow with exactly one block (a valid single-block scenario) will have the Run button permanently disabled. Additionally, the Mod+Enter keyboard shortcut handler does not check hasValidationErrors/isWorkflowBlocked, meaning the same keyboard path that fires the button handler can still execute a blocked workflow.

Confidence Score: 3/5

• Safe to merge after fixing the keyboard-shortcut bypass and reconsidering the single-block edge validation heuristic.
• The backend and deployment-hook changes are solid. The panel change introduces a genuine logic gap (keyboard shortcut bypasses the new guard) and a potentially incorrect validation condition (blocking valid single-block workflows), which together lower confidence below a straightforward merge.
• Pay close attention to panel.tsx — specifically the hasValidationErrors condition and the run-workflow keyboard command handler.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant panel.tsx
    participant use-deployment.ts
    participant use-predeploy-checks.ts
    participant deploy/route.ts
    participant validateWorkflowState

    User->>panel.tsx: Click Run button
    panel.tsx->>panel.tsx: Check hasBlocks && !hasEdges
    alt hasValidationErrors
        panel.tsx-->>User: Button disabled (no run)
    else no validation errors
        panel.tsx->>panel.tsx: handleRunWorkflow()
    end

    User->>panel.tsx: Click Deploy / Update button
    panel.tsx->>use-deployment.ts: handleDeployClick()
    use-deployment.ts->>use-predeploy-checks.ts: runPreDeployChecks(blocks, edges, loops, parallels)
    alt checks fail
        use-predeploy-checks.ts-->>use-deployment.ts: { passed: false, error }
        use-deployment.ts-->>User: Notification error
    else checks pass & isDeployed
        use-deployment.ts-->>panel.tsx: { success: true, shouldOpenModal: true }
        panel.tsx-->>User: Open redeploy modal
    else checks pass & first deploy
        use-deployment.ts->>deploy/route.ts: POST /api/workflows/[id]/deploy
        deploy/route.ts->>validateWorkflowState: validateWorkflowState(blocks, edges, loops, parallels)
        alt validation fails
            validateWorkflowState-->>deploy/route.ts: { valid: false, errors }
            deploy/route.ts-->>use-deployment.ts: HTTP 400 error
            use-deployment.ts-->>User: Notification error
        else validation passes
            deploy/route.ts->>deploy/route.ts: validateWorkflowSchedules()
            deploy/route.ts->>deploy/route.ts: deployWorkflow()
            deploy/route.ts-->>use-deployment.ts: HTTP 200 success
            use-deployment.ts-->>panel.tsx: { success: true, shouldOpenModal: true }
            panel.tsx-->>User: Open deploy modal
        end
    end

_{Last reviewed commit: a072602}