Empty Output Flow Break

Questions
1

A node executes successfully but returns no items, causing downstream nodes to process nothing

3

Hi @Fatoki_Alfred Welcome!
@Benjamin_Behrens is right about checking the data is even coming for that particular node to process, also make sure to go inside that specific node’s settings and toggle ON to Always Output Data so that even if the next node is not dependent on the previous node data the flow would still go on.

4

This is a common issue in n8n, here are a few things to check:

  1. IF node branch not connected- if the node is downstream of an IF, make sure you connected it to the correct branch
  2. Your filter/query is returning empty- your node may have ran fine but the search/filter matched nothing. Add in another IF node after to check {{$items().length>0}} and route accordingly.
  3. Wrong input data - your node may be referencing a field that is empty or undefined upstream, so it returns nothing silently. Inspect the input data by pinning it.
  4. HTTP/API node with empty response - it may be a paginated API and you might be hitting page 2+ and have no results.

Another clean way to handle this is to put a “No Operation” node on the empty path to prevent breaking the workflow.