SECURITY Signal 242
Measure time between steps in Vercel Workflows
↗
Vercel added a visual measurement tool that shows the elapsed time between any two steps in a workflow trace.
Engineers can now see exactly how long a step waited before starting, which helps identify hidden queue times or unexpected delays that inflate overall run duration. The feature is accessed through the trace viewer, so no code changes are required, but it does rely on the beta UI and specific key modifiers. Understanding these gaps can guide optimizations in step ordering, resource allocation, or concurrency settings.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The trace viewer now lets you hover between two steps to draw a line that displays the time gap.
Sequential steps show the interval from the earlier step’s end to the later step’s start; overlapping steps show the difference between their start times.
The UI works with Option on macOS or Alt on Windows/Linux and is available in the Workflows tab or via the beta CLI.
THE READ
What elseif makes of it.
Vercel’s latest update introduces an interactive timing overlay in the workflow trace viewer, allowing engineers to select any two steps and instantly see the elapsed time between them. The overlay appears as a measurement line that is drawn when a step is selected and the appropriate modifier key is held. This visual cue replaces the need to manually calculate gaps from raw timestamps.
To use the feature, you pick a step in the trace, hold the Option key on macOS or the Alt key on Windows/Linux, and then hover over another step. The line that appears reports the interval from the end of the first step to the start of the second for sequential steps, while for overlapping or nested steps it reports the difference between their start times. If no step is selected, holding the modifier still shows gaps across the entire timeline, using the same line style.
The primary benefit is quicker identification of hidden latency such as queue waits or delayed starts that are not reflected in the individual step durations. By visualizing these gaps directly in the UI, engineers can pinpoint where a workflow is spending time outside of explicit step execution, informing decisions about step parallelism, resource limits, or scheduling. This can reduce overall run times without changing the underlying workflow logic.
Adopting the measurement capability requires no changes to existing workflow definitions; you simply open a run in the Workflows tab of Vercel Observability or launch the local viewer with the beta CLI command. The feature is gated behind the beta version of the Workflow SDK, so teams need to ensure they are using the beta release to access the UI. No additional configuration or instrumentation is needed beyond the standard trace collection.
The measurement overlay is limited to the visual trace interface and does not export timing data to logs or external monitoring tools. It only works for steps within the same workflow run and relies on the modifier keys, so it may be inaccessible in environments without a keyboard (e.g., touch-only devices). Additionally, older or non-beta versions of the SDK will not display the overlay, so teams must stay on the supported version to benefit.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER