Hi @napter, error handling is indeed node specific (to some extent at least). However, the undefined value in your screenshot does look like a bug to me. Can you confirm if this issue still persists with the current version of n8n and which node exactly throws this?