RepoJournal
Vercel

@vercel

Next.js + the Vercel platform — frontend infrastructure for the web

Pick a date

The Wire · Showcase

WORKFLOW CUTS STEP LATENCY IN HALF WITH LAZY INLINE EXECUTION

By RepoJournal · Filed · About Vercel

Two performance wins collapse network round-trips per step: lazy inline step start eliminates the separate step_created call, and inline event-log delta skips redundant event.list fetches on sequential workflows.

The workflow runtime has been bleeding latency on every step. Each iteration called `loadWorkflowRunEvents` to re-read events the handler just wrote inline [1], pure network overhead on owned execution paths. Pairing that with lazy inline step start [2], which materializes steps on-the-fly instead of round-tripping `step_created` separately, collapses what was two network calls per step into one. For simple sequential workflows this is the difference between 200ms and 400ms. Meanwhile, Next.js is preparing for root params in App Shells [3], which required reworking vary params serialization in the Flight stream to survive stage rewinding [4]. On the CLI side, `vc metrics` gained timezone bucketing support for daily granularity metrics [5], and a new `vercel traces create` subcommand wraps the curl tracing flow [6]. Eve's human-in-the-loop story is now properly documented [7], with fixes landing for dynamic tool approval gates [8] and credential resolution for linked projects [9].

Action items

References

  1. [1] perf(core): skip per-step events.list via inline event-log delta ↗ vercel/workflow
  2. [2] perf(core): lazy inline step start (save one world round-trip per step) ↗ vercel/workflow
  3. [3] [App Shells] Allow root params in app shells ↗ vercel/next.js
  4. [4] Support vary params rewinding ↗ vercel/next.js
  5. [5] feat: vc metrics improvements ↗ vercel/vercel
  6. [6] [cli] add `traces create` as an alias for `curl --trace` ↗ vercel/vercel
  7. [7] docs: dedicated human-in-the-loop page ↗ vercel/eve
  8. [8] fix(eve): harness - preserve approval gates on dynamic tools ↗ vercel/eve
  9. [9] fix(eve): recognize linked-project gateway credentials ↗ vercel/eve

FAQ

What changed in Vercel on June 18, 2026?
Two performance wins collapse network round-trips per step: lazy inline step start eliminates the separate step_created call, and inline event-log delta skips redundant event.list fetches on sequential workflows.
What should Vercel teams do about it?
Review and merge workflow performance PRs 2478 and 2475 to ship the latency wins • Merge workflow Version Packages when ready to cut the release • Test Next.js App Shell root params on your local branches
Which Vercel repositories shipped on June 18, 2026?
vercel/workflow, vercel/next.js, vercel/vercel, vercel/eve

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • 14 famous open source orgs
  • One wire per day
  • Public, generic
  • Read on the web, when you remember

Your wire

  • Up to 1,500 of your repos - orgs, deps, vendors
  • Morning and evening briefs
  • Action items routed to your team
  • Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.