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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 4, 2026 5:44pm

PR Summary

Medium Risk
Changes what gets persisted to execution state by stripping childTraceSpans, which could affect any downstream blocks or UI code that previously relied on that field being present in state/output. The change is localized to BlockExecutor logging/state writing and should mainly reduce oversized LLM/tool-call context payloads.

Overview
Prevents large nested-workflow execution traces from being persisted into per-block execution state by stripping childTraceSpans before calling setBlockOutput on successful executions, while still keeping spans on blockLog for the Logs UI.

On error paths, stops adding childTraceSpans to the returned errorOutput and instead conditionally attaches spans to blockLog only when the thrown error is a ChildWorkflowError with non-empty spans.

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

Greptile Summary

This fix strips childTraceSpans from the execution state on both the success and error paths in BlockExecutor, preventing the full child workflow trace (up to 148k+ tokens) from being forwarded to downstream Agent blocks as LLM tool result context. On success, a simple destructure produces outputForState before setBlockOutput; on error, traces are read directly from ChildWorkflowError to populate blockLog.childTraceSpans without ever touching errorOutput.

Confidence Score: 5/5

Safe to merge — the core state/LLM leakage is correctly fixed with no new issues introduced.

The change is minimal and targeted. childTraceSpans is stripped from both setBlockOutput and the return value on the success path, and never placed into errorOutput on the error path. The ChildWorkflowError.childTraceSpans field is always an array (defaulted to [] in the constructor), so the .length > 0 guard is safe. The only open item is the pre-existing cosmetic duplication of childTraceSpans inside blockLog.output on the success path (noted in a prior review comment), which does not affect the LLM token fix.

No files require special attention; the single changed file is well-contained.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Handler as Block Handler
    participant BE as BlockExecutor
    participant State as BlockStateWriter
    participant Log as blockLog (Logs UI)
    participant LLM as LLM Tool Context

    Handler->>BE: returns normalizedOutput (with childTraceSpans)
    BE->>Log: blockLog.output = filterOutputForLog(normalizedOutput)
    BE->>BE: destructure → outputForState (childTraceSpans stripped)
    BE->>State: setBlockOutput(outputForState)
    BE->>LLM: return outputForState (no childTraceSpans)

    Note over State,LLM: Traces never reach LLM tool result context

_{Reviews (2): Last reviewed commit: "fix(executor): return stripped output so..." | Re-trigger Greptile}

@greptile

@cursor review