fix(workflows): hold the v2 sync run result until its execution log is finalized

[waleedlatif1]

Summary

A run-from-block call that names a just-finished v2 sync run as its source can fail with NOT_FOUND: No execution state found for source run. CI hit this in e2e (stop-after) (run 38262284889, attempt 1; it passed on rerun), and any v2 API, CLI or MCP caller can hit it the same way.

Cause. After a run finishes, the core writes its log and saved execution state in a background step (execution-core.ts). runSynchronousWorkflow in execute-service.ts returned the completed result without waiting for that step. Run-from-block reads the state from the primary DB, found the log row with no state yet, and returned 404. In the CI log the source run passed at 14:24:52.750 and the CLI failed at 14:24:53.773, while the write was still in flight.

Fix. Await loggingSession.waitForPostExecution() in runSynchronousWorkflow's finally, as the legacy execute route already does ("the sync response is the run's receipt"). It covers completed, failed, cancelled, timed-out and thrown runs, and does nothing after a pause. The wait swallows errors and the background step always settles, so it can't hang the response. This is not a retry.

Trade-off. v2 sync responses now include the time to save the log, the same as the legacy route.

Test plan

• CI e2e (stop-after) and the v2 execute suites

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 12, 2026 7:49pm UTC

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.

Turn on auto-fix | Re-trigger cubic</sub>

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Holds synchronous workflow results until the core's post-execution work finishes.

• Synchronous workflow results wait for their logs and saved state.

Diagram

sequenceDiagram
  participant Caller
  participant Service as executeWorkflowService
  participant Core as executeWorkflowCore
  participant Log as LoggingSession
  Caller->>Service: Execute synchronously
  Service->>Core: Execute with loggingSession
  Core->>Log: Register finalization promise
  Core-->>Service: Run result or error
  Service->>Log: waitForPostExecution()
  Log-->>Service: Post-execution work settled
  Service-->>Caller: Terminal result

Loading

_{Reviews (1) · Last reviewed commit: "fix(workflows): hold the v2 sync run res..." · Reviewed by Greptile}