# drop_on

> 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)

---
title: drop_on
latest-operator-version: v26.1.4
latest-console-tag: v3.7.3
latest-connect-version: 4.93.0
latest-redpanda-tag: v26.1.9
docname: connect/components/outputs/drop_on
page-component-name: cloud-data-platform
page-version: master
page-component-version: master
page-component-title: Cloud
page-relative-src-path: connect/components/outputs/drop_on.adoc
page-edit-url: https://github.com/redpanda-data/cloud-docs/edit/main/modules/develop/pages/connect/components/outputs/drop_on.adoc
page-git-created-date: "2024-09-09"
page-git-modified-date: "2026-05-26"
---

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

**Available in:** Cloud, [Self-Managed](https://docs.redpanda.com/connect/components/outputs/drop_on/%20%22View%20the%20Self-Managed%20version%20of%20this%20component%22)

Attempts to write messages to a child output and if the write fails for one of a list of configurable reasons the message is dropped (acked) instead of being reattempted (or nacked).

```yml
outputs:
  label: ""
  drop_on:
    error: false
    error_patterns: [] # No default (optional)
    back_pressure: "" # No default (optional)
    output: "" # No default (required)
```

Regular Redpanda Connect outputs will apply back pressure when downstream services aren’t accessible, and Redpanda Connect retries (or nacks) all messages that fail to be delivered. However, in some circumstances, or for certain output types, we instead might want to relax these mechanisms, which is when this output becomes useful.

## [](#fields)Fields

### [](#back_pressure)`back_pressure`

An optional duration string that determines the maximum length of time to wait for a given message to be accepted by the child output before the message should be dropped instead. The most common reason for an output to block is when waiting for a lost connection to be re-established. Once a message has been dropped due to back pressure all subsequent messages are dropped immediately until the output is ready to process them again. Note that if `error` is set to `false` and this field is specified then messages dropped due to back pressure will return an error response (are nacked or reattempted).

**Type**: `string`

```yaml
# Examples:
back_pressure: 30s

# ---

back_pressure: 1m
```

### [](#error)`error`

Whether messages should be dropped when the child output returns an error of any type. For example, this could be when an `http_client` output gets a 4XX response code. In order to instead drop only on specific error patterns use the `error_matches` field instead.

**Type**: `bool`

**Default**: `false`

### [](#error_patterns)`error_patterns[]`

A list of regular expressions (re2) where if the child output returns an error that matches any part of any of these patterns the message will be dropped.

**Type**: `array`

```yaml
# Examples:
error_patterns:
  - "and that was really bad$"

# ---

error_patterns:
  - "roughly [0-9]+ issues occurred"
```

### [](#output)`output`

A child output to wrap with this drop mechanism.

**Type**: `output`

nclude::connect:components:partial$examples/outputs/drop\_on.adoc\[\]