Test n8n in execute step very slow is it normal?

أسئلة
1

Test n8n in execute step very slow is it normal?

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

It can be normal for “Execute step” (partial executions) to feel slower, especially on larger workflows or after idle periods.

  • Partial executions send extra data/metadata to the backend and can hit size limits or overhead that full runs don’t have. Use a Manual Trigger and run the whole workflow when possible, or temporarily limit data during testing to reduce payload size (Manual, partial, and production executions).

  • Large data in the editor are slower because the UI must stream and render execution data. For heavy runs, execute in the background (active workflow via webhook/schedule) rather than through the editor UI (UI lag on large loops).

  • First runs after idle (“cold”) can be slower; similar reports show initial latency that improves on subsequent runs (first-run slowness examples).

  • If you see timeouts or long node times, reduce items per run (Split in Batches), avoid heavy Code nodes where built-in nodes suffice, and ensure adequate resources; increase execution timeout if needed when self-hosting (heap/memory and batching advice).