Hey @cmdntd987, could you share the JSON data of a workflow using which the “workflow simply gets stuck” problem can be reproduced? The simpler the better. You can simply copy from your n8n canvas and paste here on the forum.
Or is this simply the problem of an error occurring but the message not being shown? This problem should be fixed with the upcoming release: Custom node not showing error after update to 0.181.1 - #10 by jan
Until then you might want to downgrade to a previous n8n version seeing how much this impacts you.