IF Node skips 1 of 3 items even though all have valid input (n8n Version 1.99.1)

I have a workflow that processes multiple YouTube videos and sends them to a local transcription service via HTTP POST. The response from the transcription service (studio_transcript_m) contains 3 valid items, all with status: 0.

These 3 items are passed to an IF node (If_no_err) that checks:

{{ $json.status }} is equal to 0

However, in the execution trace:

  • Only 2 items are processed by the IF node (both correctly)
  • The execution ends with the message:
    :red_circle: “Workflow execution had an error — The execution was cancelled”

But:

  • I did not manually cancel the execution (it happened during the night)
  • All inputs and outputs are valid JSON
  • No node shows an error
  • The transcription step for all 3 items completed successfully (confirmed by output logs)

It seems n8n cancelled the execution after 2 of 3 items were passed to the IF node, before the last one could be evaluated.

What is the error message (if any)?

Workflow execution had an error – The execution was cancelled
(No node failed, and no error stack is shown)

Share the output returned by the last node

One of the successful transcription results:

{
  "status": 0,
  "id": "LJnchPGJ_os",
  "transcription": {...
  }
}

All 3 items look like this, and all have status: 0.

Information on your n8n setup

  • n8n version: 1.99.1
  • Database: PostgreSQL
  • n8n EXECUTIONS_PROCESS setting: own
  • Running n8n via: Docker
  • Operating system: macOS

:magnifying_glass_tilted_right: My question:

Why would n8n cancel an execution after 2 of 3 items were already processed by an IF node?

Could this be:

  • A timeout or memory limit reached during evaluation?
  • A problem in the execution engine when handling long-running requests?
  • Something else I can debug or catch earlier?

Happy to provide logs, workflow JSON, or screenshots if helpful.

Thanks in advance!

Hey @MacMax777 hope all is well, welcome to the communioty.

Could you please share some details - show a screenshot of such execution from the logs, show some inputs and outputs (where there are three inputs, but only two outputs), share how long does it take to run the whole workflow, how much binary does this workflow deal with etc.


I believe I found the issue. The workflow had a timeout setting of 1 hour. It wasn’t immediately obvious because the execution was canceled at around 1h 4m, so I didn’t make the connection at first.

It would be much clearer if the error message explicitly stated that the execution was stopped due to a timeout — currently, it’s not obvious at all.

I’ll report back if it turns out that the cancellation was caused by something else.
Thanks for your attention!

This is exactly why I asked how long it takes. Please fee to open a but for clearer error message for executions which time out. Cheers.