{
  "schema_version": "1.1",
  "id": "s4:https://vercel.com/changelog/measure-time-between-steps-in-vercel-workflows",
  "slug": "measure-time-between-steps-in-vercel-workflows-0dtmqf6",
  "url": "https://feed7.dev/p/measure-time-between-steps-in-vercel-workflows-0dtmqf6",
  "title": "Measure time between steps in Vercel Workflows",
  "why_included": "Vercel’s workflow trace viewer can measure gaps between steps, helping distinguish slow task execution from delayed starts and queue waits in agent workflows.",
  "summary": "The Vercel Workflows trace viewer can now measure time between any two steps. Select one step, hold **Option on macOS or Alt on Windows and Linux**, and hover another to draw the measurement.",
  "practical_implication": "Use the gaps to investigate runs whose total duration exceeds the visible work. For sequential steps, the viewer measures end-to-start delay; for overlapping or nested steps, it compares start times. With nothing selected, the modifier reveals gaps across the timeline.",
  "agent_context": "The Vercel Workflows trace viewer can now measure time between any two steps. Select one step, hold **Option on macOS or Alt on Windows and Linux**, and hover another to draw the measurement.\n\nUse the gaps to investigate runs whose total duration exceeds the visible work. For sequential steps, the viewer measures end-to-start delay; for overlapping or nested steps, it compares start times. With nothing selected, the modifier reveals gaps across the timeline.\n\nThe feature exposes timing relationships but does not identify their cause. A visible delay may indicate a queued or delayed start, but the material does not describe automatic diagnosis, alerts, or historical aggregation.",
  "source": {
    "name": "Vercel",
    "url": "https://vercel.com/changelog/measure-time-between-steps-in-vercel-workflows",
    "published_at": "2026-08-05T00:00:00.000Z"
  },
  "source_class": "blog_post",
  "content_type": "Engineering Post",
  "layer": "infra",
  "domains": [
    "coding"
  ],
  "topics": [
    "observability"
  ],
  "verification": {
    "status": "official_source",
    "label": "Official Source",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "The feature exposes timing relationships but does not identify their cause. A visible delay may indicate a queued or delayed start, but the material does not describe automatic diagnosis, alerts, or historical aggregation."
  ],
  "connected_context": {
    "meaning": "This adds a precise manual way to locate unexplained time inside a workflow trace, narrowing investigation from total duration to specific inter-step or overlapping-start gaps. It improves diagnosis but not attribution or remediation: teams still need other telemetry and operational logic to determine whether a measured delay came from queuing, execution, routing, or another cause.",
    "corpus_size": 368,
    "generated_at": "2026-08-06T10:04:21.917Z",
    "connections": [
      {
        "title": "Export AI Gateway traces with Vercel Drains",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/export-ai-gateway-traces-with-vercel-drains",
        "feed7_url": "https://feed7.dev/p/export-ai-gateway-traces-with-vercel-drains-0enwlg4",
        "reason": "Workflow gap measurements locate delay between steps, while exported Gateway traces can explain latency, routing, and retries inside an inference request that occupies part of that timeline."
      },
      {
        "title": "Agent Runs now available in the Vercel MCP and CLI",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/agent-runs-vercel-mcp-cli",
        "feed7_url": "https://feed7.dev/p/agent-runs-vercel-mcp-cli-06cfo04",
        "reason": "Agent Runs exposes reasoning and tool-call traces to coding agents; the workflow viewer adds a complementary human inspection of timing relationships around such work."
      },
      {
        "title": "AI Gateway logs now have a dedicated page",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/ai-gateway-logs",
        "feed7_url": "https://feed7.dev/p/ai-gateway-logs-1272t5j",
        "reason": "Gateway logs provide request-level latency and fallback evidence that can help interpret a workflow gap, while the new measurement feature alone cannot identify its cause."
      },
      {
        "title": "How Forward Deployed Engineering is done at Factory — Eno Reyes",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=wpOA-UXynoM",
        "feed7_url": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-factory-eno-reyes-0zgscmd",
        "reason": "Factory’s workflow-design approach makes instrumentation a prerequisite for bounded autonomy; explicit inter-step timing supplies one additional measurement for finding where an instrumented path stalls."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-08-05T00:00:00.000Z",
  "modified_at": "2026-08-05T00:00:00.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/measure-time-between-steps-in-vercel-workflows-0dtmqf6",
    "json": "https://feed7.dev/p/measure-time-between-steps-in-vercel-workflows-0dtmqf6.json",
    "markdown": "https://feed7.dev/p/measure-time-between-steps-in-vercel-workflows-0dtmqf6.md"
  }
}