Are these 2 billed/counted equal:
1 workflow execution going from trigger to last action
1 workflow execution that stops at the second node (as below)?
I have SO many executions, because of the way I receive events from Asana, but.. just curious if those 2 workflow executions mentioned above are “billed”/counted equal.
Thanks a lot, and super happy with N8N, just wanna know 
@dalynn N8n tracks an execution as soon as the workflow is triggered, even if the workflow is terminated early. This means that a workflow that terminates early, say at node 2, is charged the same as one that terminates at the final node. For tools like Asana, which emit many events, the solution is often to filter as early as possible or rethink the triggers to avoid unnecessary executions. Would be happy to share how we reduced the number of executions without losing the events.
Hope this helps, cheers!
Would be great! please share, thanks.
Okay so alternatively, you can try using self hosted n8n on Hostinger. This way, the execution limit will be unlimited.
Hope this helps! and you can also refer to this as well-
Let me know if you found this helpful.
Executions are counted as soon as the workflow is triggered.
So even if it stops early (for example at a filter), it’s still billed as one execution.
Filtering early helps with performance, but it doesn’t reduce execution count.
As others have said the amount is per triggered workflow.
Sadly there is no way around it.
So you can define a mor strict event trigger on the asana side. Not sure what is actually possible.
Or maybe something like hookdeck. This might also allow some basic filtering.
Cloudflare workers is also an option but requires coding.
Also are you on cloud or selfhosted with a license?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
