anchor.diff:  .A Spring Cloud Stream Sink Application with Custom and Global Error Handlers
   image::custom_vs_global_error_channels.png[width=300,scaledwidth="50%"]
   
  -For each input binding, Spring Cloud Stream creates a dedicated error channel with the following semantics `<channel-name>.<group-name>.errors`.
  -If such a channel has a subscriber, all errors are sent to that subscriber.
  +For each input binding, Spring Cloud Stream creates a dedicated error channel with the following semantics `<destinationName>.errors`.
  +
  +NOTE: The `<destinationName>` consists of the name of the binding (such as `input`) and the name of the group (such as `myGroup`).
   
   Consider the following:
   
  
positive.code: }
  ----
  
  The `handle(..)` method, which subscribes to the channel named `input`, throws an exception.  Given there is also a subscriber to the error channel `input.myGroup.errors`
  all error messages are handled by this subscriber.
  
  
negative.code: 
  This may be a convenient option if error handling logic is the same regardless of which handler produced the error.
  
  Also, error messages sent to the `errorChannel` can be published to the specific destination at the broker by configuring a binding named `error` for the outbound target.
  This option provides a mechanism to automatically send error messages to another application bound to that destination or for later retrieval (for example, audit).
  For example, to publish error messages to a broker destination named `myErrors`, set the following property:
  
  