It's an inherited issue from node-red-contrib-chromecast
which really needs sorting.
I highlighted this in a previous post, and raised an issue here.
This potentially could be a popular contrib-node, as it engages node-RED with Google Home & Chromecast which is a common forum request.
Any help with error handling would really benefit the community...
Paul