Hi Harshil! Thanks for the quick reply!
I see that but it allows the item that failed to continue on as well. Which would not be possible if let’s say the next node depends on the outputs of the node what is faced with some failure.
I believe commercial solutions out there like integromat will treat each item discreetly, and hence, which ever item that failed, doesn’t continue, while other items continue normally.
Seems like n8n will simply not have this function I guess? My concern is with one of those 404 or occassional 500 returns from an app, which is not uncommon and throws everything else unnecessarily off.