Measure time between steps in Vercel Workflows Makes Delays Visible.

A workflow can spend several seconds doing apparently nothing. Vercel now gives developers a way to investigate that missing time without leaving the trace viewer.

The company has added Measure time between steps in Vercel Workflows, a timeline inspection feature for Vercel Workflows and the Workflow SDK. As detailed in the official changelog, developers can compare any two steps in a workflow run and see the elapsed time represented by a measurement line.

The update, posted on August 5, 2026, is aimed at a common observability blind spot. Individual step durations may look reasonable even when the complete workflow takes considerably longer. The discrepancy can come from delayed starts, scheduling overhead, or time spent waiting in a queue between operations.

The interaction is built directly into the existing trace viewer. A developer selects one step, holds Option on macOS or Alt on Windows and Linux, then hovers over another step. Vercel draws a line between the selected points and displays the measured interval.

The calculation changes according to the relationship between the steps:

• Sequential steps: The viewer measures from the end of the earlier step to the start of the later step. This exposes idle time between two operations rather than combining their execution durations.
• Overlapping or nested steps: The measurement compares the steps’ start times. That can help developers understand when concurrent work began and whether a nested operation started later than expected.
• No selected step: Holding the relevant modifier key reveals gaps across the timeline using the same measurement-line interface.

That distinction matters. The feature is not simply another display of how long each function or task ran. It measures the temporal relationship between steps, including periods not attributed to the execution of either step.

For a small team operating a long-running workflow, a few seconds of unaccounted time can compound across multiple tasks or customer requests. A content pipeline might wait between generation and publishing. An onboarding process could pause before sending an email. An AI workflow may complete a model call quickly but then sit idle before its next tool operation begins.

Previously, diagnosing those patterns could require comparing timestamps manually or exporting telemetry into another observability system. The new trace interaction makes an initial investigation faster because the relevant gaps are visible within the context of the workflow run.

It should also make performance discussions more precise. If a run is slow because one step takes 20 seconds, the remediation is likely inside that step. If the steps are individually fast but separated by long gaps, the team can instead investigate queue waits, delayed starts, orchestration logic, or resource availability.

There are limits to what the interface itself establishes. A measurement line shows when a delay occurred, but Vercel’s announcement does not say that it automatically identifies the underlying cause. Developers may still need logs, step metadata, and application-level tracing to determine why a gap appeared.

The feature is available from a workflow run opened through the Workflows tab in Vercel Observability. Developers using the Workflow SDK locally can access the viewer by running:

npx workflow@beta web

No application code changes are described as necessary for using the measurement interaction. Teams can open an existing trace, select a step, and compare it with another point in the run.

The update is small compared with a new runtime or deployment product, but it addresses a practical debugging problem. Workflow performance depends on more than the duration of visible tasks. Making the spaces between those tasks measurable gives developers a clearer account of where a run’s time actually went.

What is Measure time between steps in Vercel Workflows?

It is a trace-viewer feature that measures elapsed time between two workflow steps. It can reveal delayed starts, queue waits, and other gaps that are not explained by the execution duration of individual steps.

How is the measurement activated?

Select a step, hold Option on macOS or Alt on Windows and Linux, then hover over another step. With no step selected, holding the modifier key shows gaps across the workflow timeline.

Where is the feature available?

Developers can use it when viewing a workflow run from the Workflows tab in Vercel Observability. It is also accessible locally through the Workflow SDK viewer by running npx workflow@beta web. Vercel’s announcement does not specify plan requirements or separate pricing.