Will error handling workflows (starting with the error trigger node) when invoked, be considered a separate execution for purposes of calculating execution limits/quota?

Questions
1

There is explicit mention of sub workflows not being counted as a separate execution - for execution limit calculations. Would this also be the case for error handling workflows (triggered by error trigger node)?
Sub-workflows | n8n Docs.._gaMTM1NDk4MjcyOC4xNzYyMTY2NzAz*_ga_0SC4FF2FH9*czE3NjYxMzU5MDIkbzQyJGcxJHQxNzY2MTM1OTQ3JGoxNSRsMCRoMA..

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

@Prashanth1 there is no clear or explicit statement about whether error handling workflows count toward execution limits. The documentation that clarifies this point for sub workflows does not mention error workflows.

3

Hi @Prashanth1

No, Error Handling workflows (triggered by the Error Trigger node) do not count as a separate execution.

Just like sub-workflows, an error handler is treated as an extension of the original process. Even if your main workflow fails and triggers an error workflow, it is billed and recorded as one single execution total.

If you found my answer helpful, please like and accept it.