reject

Available in: Cloud, Self-Managed

Rejects all messages, treating them as though the output destination failed to publish them.

# Config fields, showing default values
output:
  label: ""
  reject: ""

The routing of messages after this output depends on the type of input it came from. For inputs that support propagating nacks upstream such as AMQP or NATS the message will be nacked. However, for inputs that are sequential such as files or Kafka the messages will simply be reprocessed from scratch.

To learn when this output could be useful, see [the Examples.

Examples

  • Rejecting Failed Messages

This input is particularly useful for routing messages that have failed during processing, where instead of routing them to some sort of dead letter queue we wish to push the error upstream. We can do this with a switch broker:

output:
  switch:
    retry_until_success: false
    cases:
      - check: '!errored()'
        output:
          amqp_1:
            urls: [ amqps://guest:guest@localhost:5672/ ]
            target_address: queue:/the_foos

      - output:
          reject: "processing failed due to: ${! error() }"