Hi @akg17 ,
You are correct that messages get published directly the the error queue w/ the info being in @giri 's post. I think if we went back several years to design this again we might consider publishing error messages to a topic, but sending errors to a specific queue is really the one use case where I do think it sometimes makes sense to not publish to a topic.
That said, what are your options if you want to have multiple consumers be able to receive these messages that are currently going to the error queue?
Don’t actually publish your messages to the error queue. Instead handle the errors yourself and use StreamBridge to publish them to dynamic topics of your choice. The benefit of this route is that it’s actually more flexible b/c it allows you to publish messages that have different error situations to different topics to be handled in different ways. If you still want to use the error queue provided by the binder there is another work around. Internally to the broker when a message is published to a queue it actually gets sent to a “Network Topic” first. These network topics live in a Solace reserved topic space. For queues the format of their network topics is: #P2P/QUE/<Queue_Name> So a work around is to have your apps listen to that topic and they will be able to receive their own copy of the error message. You can find the network topic for your queue in PubSub+ Manager under the Queue detail information. (It would also be findable via cli or SEMP in the queue details). Note that is a work around so don’t go using this information in all of your apps. In practice Solace could decide to change it so the network topic changes for a queue as this is an internal implementation detail in a reserved space, but I think it’s pretty safe to use as I believe it’s been that way for over 10 years 
Hope that helps!
