n8n - 💡(How to fix) Fix Feature: Per-node execution timestamp overlay on canvas during workflow run

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Show per-node execution timestamps (start time, duration, end time) directly on the workflow canvas during and after a workflow run.

Root Cause

Show per-node execution timestamps (start time, duration, end time) directly on the workflow canvas during and after a workflow run.

RAW_BUFFERClick to expand / collapse

Summary

Show per-node execution timestamps (start time, duration, end time) directly on the workflow canvas during and after a workflow run.

Problem to solve

When debugging a workflow with many nodes, identifying which node took longest or why a workflow ran slowly requires drilling into execution logs or export data. There is no at-a-glance way to see execution timing directly on the canvas.

Proposed solution

During workflow execution, display small timing badges on each node card:

  • Show duration (e.g. "1.2s") after node completes
  • Color-code by speed (green/yellow/red threshold)
  • After full run, show accumulated timing overlay accessible via hover

This would help users identify bottlenecks without leaving the canvas or exporting logs.

Alternatives considered

  • Exporting execution data to analyze in external tools - requires extra steps
  • Right-click node > View execution data - requires navigation
  • Existing execution log view - list-based, not spatial

Impact

  • Affected: Workflow builders debugging performance or explaining timing to stakeholders
  • Severity: Annoying / blocks efficient debugging
  • Frequency: Intermittent (when performance issues arise)
  • Consequence: +minutes per debugging session without this feature

Evidence/examples

Related issues:

  • #28922 (Version History) - debugging workflow behavior
  • #30358 (Code node hangs with AI Agent) - timing-related debugging
  • #5298 (Redo functionality) - UX improvements for workflow editing

This is a low-effort, high-clarity improvement for workflow observability.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING