---
title: reject_errored
page-cloud: true
latest-operator-version: v26.2.6
latest-console-tag: v3.14.0
latest-connect-version: 4.118.0
latest-redpanda-tag: v26.2.7
docname: connect/components/outputs/reject_errored
page-component-name: cloud-data-platform
page-version: master
page-component-version: master
page-component-title: Cloud
page-relative-src-path: connect/components/outputs/reject_errored.adoc
page-edit-url: https://github.com/redpanda-data/cloud-docs/edit/main/modules/develop/pages/connect/components/outputs/reject_errored.adoc
description: Rejects messages that have failed their processing steps, resulting in nack behavior at the input level, otherwise sends them to a child output.
page-self-managed-available: "true"
page-self-managed-available-url: https://docs.redpanda.com/connect/components/outputs/reject_errored/
page-git-created-date: "2024-09-09"
page-git-modified-date: "2026-10-19"
page-generated-sources:
  - include: connect:components:partial$descriptions/outputs/reject_errored.adoc
    generator: null
    version: null
    source: the component specs in https://github.com/redpanda-data/connect
page-generated-content: partial
---

# reject_errored

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [cloud-data-platform-full.txt](https://docs.redpanda.com/cloud-data-platform-full.txt)

<!-- Source: https://docs.redpanda.com/cloud-data-platform/develop/connect/components/outputs/reject_errored.md -->

Rejects messages that have failed their processing steps, resulting in nack behavior at the input level, otherwise sends them to a child output.

The routing of messages rejected by 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.

#### Common

```yml
output:
  label: ""
  reject_errored: {}
```

#### Advanced

```yml
output:
  label: ""
  reject_errored: {}
```

## Examples

### Rejecting Failed Messages

The most straight forward use case for this output type is to nack messages that have failed their processing steps. In this example our mapping might fail, in which case the messages that failed are rejected and will be nacked by our input:

```yaml
input:
  nats_jetstream:
    urls: [ nats://127.0.0.1:4222 ]
    subject: foos.pending

pipeline:
  processors:
    - mutation: 'root.age = this.fuzzy.age.int64()'

output:
  reject_errored:
    nats_jetstream:
      urls: [ nats://127.0.0.1:4222 ]
      subject: foos.processed
```

### DLQing Failed Messages

Another use case for this output is to send failed messages straight into a dead-letter queue. You use it within a [fallback output](https://docs.redpanda.com/cloud-data-platform/develop/connect/components/outputs/fallback/) that allows you to specify where these failed messages should go to next.

```yaml
pipeline:
  processors:
    - mutation: 'root.age = this.fuzzy.age.int64()'

output:
  fallback:
    - reject_errored:
        http_client:
          url: http://foo:4195/post/might/become/unreachable
          retries: 3
          retry_period: 1s
    - http_client:
        url: http://bar:4196/somewhere/else
        retries: 3
        retry_period: 1s
```