# Recovering a Kafka Connector From a Poison Pill with Conduktor Agents

Restarting a failed Kafka Connect task takes seconds. Figuring out why it keeps failing, and whether it's safe to skip the record that's stopping it, takes more work. [Kafka Connect](https://www.conduktor.io/glossary/kafka-connect-building-data-integration-pipelines) resumes from its committed offset, so if the next record is the problem, another restart brings the task back to the same failure.

This is our second Conduktor Agents use case. In the first, Bob and Priya investigated a leaked Kafka credential. This time, they're trying to get a reporting pipeline running again without losing data nobody can account for.

The pipeline is `postgres-sink`, which reads the `pageviews` topic and writes to Postgres. It expects Avro. Jack, on another team, is testing a new pageview event and sends `{"viewtime": "yesterday", "userid": "User_9", "pageid": "Page_42"}` through Console's Produce tab, leaving its value format at the default, JSON.

Bob's team runs the connector. He can restart it, stop it, and reset its consumer group's offsets, but he can't read the audit log or change the connector's configuration. Priya, on the platform team, can do both. As in the first use case, the fix needs both of them.

## Bob Restarts the Task. It Fails Again.

Within a minute, `postgres-sink` has one failed task. The error ends in `Unknown magic byte!`. Its Avro converter expected a Schema Registry wire-format header and didn't find one. That explains the kind of failure, but not which record caused it or how it got there.

Bob presses **Restart Task**. It fails again. He tries once more, with the same result. The task keeps returning to the bad record rather than getting past it.

> **Every film here is live HTML.** Click one to pause it and scroll to read every line, or step through it with the bar underneath.

Console

Home

Topics

Analytics

Insights

Chargeback

Governance

Application Catalog

Topic Catalog

Resource policies

Data quality

Settings
main

pageviews

records**735,131**  topic size**105 MiB**  replication factor**3**  min isr**1**  is compacted**No**

Add label

Consume Produce Configuration Consumer Groups Schema ACL Partitions*1* Alerts*0* Graphs

Produce rate Consume rate   1H 1D 7D 30D Alerts *(0)*

20 msg/s 15 msg/s 10 msg/s 5 msg/s 0

**************

12:00 15:00 18:00 21:00 00:00 03:00 06:00 09:00

Records Disk usage   1H 1D 7D 30D Alerts *(0)*

800k 700k 600k 500k 400k 300k 200k 100k 0

**********************

12:00 15:00 18:00 21:00 00:00 03:00 06:00 09:00

**Key**

**Value**

JSON Generate once

1
**{** **"****v****i****e****w****t****i****m****e****"** **:** **** **"****y****e****s****t****e****r****d****a****y****"** **,** **** **"****u****s****e****r****i****d****"** **:** **** **"****U****s****e****r****_****9****"** **,** **** **"****p****a****g****e****i****d****"** **:** **** **"****P****a****g****e****_****4****2****"** **}**

  Import CSV Produce

**No records produced**

Timestamp Key Value Schema ID

2026-11-16 10:30:54  {"viewtime":"y…

 Local Kafka local-kafka-cluster  Topics / pageviews

Search⌘K   JJ

Console

Home

Topics

Schema registry

Consumer groups

Kafka Connect

Service accounts

Analytics

Insights

Governance

Application Catalog

Topic Catalog

Resource policies

Data quality

Settings
main

postgres-sink

status Running  type **JdbcSinkConnector**  auto-restart**Disabled**  topics**1**

Add label

Overview Configuration Offsets Auto-restart Alerts*0*

Failed tasks (Last 24hrs)  Alerts *(0)*

4 3 2 1

**************

11 12 13 14 15 16 17 18 19 20 21 22 23 00 01 02 03 04 05 06 07 08 09 10

Failed tasks (Last 90 days)  Alerts *(0)*

Mon Tue Wed Thu Fri Sat Sun

***************************************************************************************************************************************************************************************1*************

September October November

Search by name 1-1 of 1

Task ID Worker State

Task-0 Show error details Hide error details connect:8083 Failed

*1*org.apache.kafka.connect.errors.ConnectException: Tolerance exceeded in error handler

*2*at org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndHandleError(RetryWithToleranceOperator.java:259)

*3*at org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execute(RetryWithToleranceOperator.java:179)

*4*at org.apache.kafka.connect.runtime.WorkerSinkTask.convertAndTransformRecord(WorkerSinkTask.java:558)

*5*at org.apache.kafka.connect.runtime.WorkerSinkTask.convertMessages(WorkerSinkTask.java:532)

*6*at org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:358)

*7*at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:261)

*8*at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:225)

*9*at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:243)

*10*at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:298)

*11*at org.apache.kafka.connect.runtime.isolation.Plugins.lambda$withClassLoader$1(Plugins.java:251)

*12*at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

*13*at java.base/java.util.concurrent.FutureTask.run(Unknown Source)

*14*at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

*15*at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

*16*at java.base/java.lang.Thread.run(Unknown Source)

*17*Caused by: org.apache.kafka.connect.errors.DataException: Failed to deserialize data for topic pageviews to Avro:

*18*at io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:169)

*19*at org.apache.kafka.connect.runtime.WorkerSinkTask.lambda$convertAndTransformRecord$4(WorkerSinkTask.java:560)

*20*at org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndRetry(RetryWithToleranceOperator.java:207)

*21*at org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndHandleError(RetryWithToleranceOperator.java:243)

*22*... 14 more

*23*Caused by: org.apache.kafka.common.errors.SerializationException: Error deserializing schema ID

*24*at io.confluent.kafka.serializers.schema.id.DualSchemaIdDeserializer.deserialize(DualSchemaIdDeserializer.java:49)

*25*at io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer$DeserializationContext.<init>(AbstractKafkaAvroDeserializer.java:434)

*26*at io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer.deserializeWithSchemaAndVersion(AbstractKafkaAvroDeserializer.java:296)

*27*at io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer.deserializeWithSchemaAndVersion(AbstractKafkaAvroDeserializer.java:272)

*28*at io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer.deserializeWithSchemaAndVersion(AbstractKafkaAvroDeserializer.java:266)

*29*at io.confluent.connect.avro.AvroConverter$Deserializer.deserialize(AvroConverter.java:231)

*30*at io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:140)

*31*... 17 more

*32*Caused by: java.lang.IllegalArgumentException: Unknown magic byte!

*33*at io.confluent.kafka.serializers.schema.id.SchemaId.fromBytes(SchemaId.java:70)

*34*at io.confluent.kafka.serializers.schema.id.DualSchemaIdDeserializer.deserialize(DualSchemaIdDeserializer.java:47)

*35*... 23 more

*36*​

 Local Kafka local-kafka-cluster  Kafka Connect / Local Connect / postgres-sink

Search⌘K   BB

**Task restarted successfully**

*Jack sends the test record, the connector fails, and Bob's restarts land on the same error.*

Those restarts also leave a trail. Priya already runs the built-in **Connector recovery** task as an agent, triggered by connector actions such as restarts. Each time Bob restarts, it escalates instead of proposing another restart, and its answer to the fourth is plain: "A restart cannot fix it: the task will read the same record again and fail again."

## Bob Finds the Record, but Not Who Sent It

Bob opens Claude Code in the team's repo and asks: "postgres-sink keeps failing. I restarted its task twice and it failed again both times. What's wrong with it?"

His assistant uses the [Conduktor MCP server](https://www.conduktor.io/mcp) with Bob's own token, so it can investigate the connector with his permissions. It reads the connector's state, then checks its [consumer group](https://www.conduktor.io/glossary/kafka-consumer-groups-explained), `connect-postgres-sink`. At partition 0, offset `735233`, it finds a plain JSON record sitting between two Avro records. That's the record the task can't deserialize.

The message also has an `app_name: Conduktor` header. Bob's assistant points out that it looks like something produced by hand through Console, but the header alone doesn't establish who sent it.

   ~/reporting

**Claude Code** v2.1.325

Opus 5.5

~/reporting

Called conduktor 2 times (ctrl+o to expand)

 The task fails with Unknown magic byte!. The connector expects Confluent Avro, so I'll check what's actually on the pageviews topic.

Called conduktor 6 times (ctrl+o to expand)

 I found it. A single bad record on pageviews breaks the connector, and restarting can't get past it.

**What's wrong**

… That record is at partition 0, offset **735233**:

Offset Format Value 735232 Avro (schema 3) {"viewtime": 7339581, "userid": "User_4", ...} **735233** **plain JSON, no schema** {"viewtime":"yesterday","userid":"User_9","pageid":"Page_42"} 735234 Avro (schema 3) {"viewtime": 7339591, "userid": "User_3", ...}

It was written at 15:30:54 today. … That looks like a test message sent by hand from Conduktor Console's producer.

**Why restarting didn't help**

The connector's last saved position is exactly 735233. Each restart picks up from there, reads the same bad record and fails again.

**How to fix it**

1. **Skip the bad record.** The connector's consumer group (connect-postgres-sink) has no active members right now because the task is down, so you can move its position to 735234 and then restart the task:

kafka-consumer-groups --bootstrap-server kafka-1:9092 \

--group connect-postgres-sink --topic pageviews:0 \

--reset-offsets --to-offset 735234 --execute

You can also do this from the consumer group page in Console.

2. **Stop one bad record from halting the connector again.** Add these settings so bad records go to a separate "dead letter" topic instead of killing the task:

errors.tolerance=all

errors.deadletterqueue.topic.name=dlq-postgres-sink

errors.deadletterqueue.context.headers.enable=true

errors.log.enable=true

I can apply the error-handling config change for you. It updates the running connector, so I'll wait for your go-ahead. I can also check the audit log to see who sent the test message.

 38s

Called conduktor 2 times (ctrl+o to expand)

 I couldn't check the audit log because the account I'm connected to Conduktor with doesn't have audit-log access (it's missing the platform.auditlog.read permission). So I can't tell you who sent the record.

A Console admin can look it up, or grant that permission to this account so I can query it. …

Fixing the connector doesn't depend on knowing who sent it. Skipping offset 735233 or adding the dead-letter-topic settings will get postgres-sink running again.

 10s

*Claude Code locates the record at the failing offset, compares it with its neighbours, then reaches the limit of Bob's audit-log permissions.*

Bob has three ways forward, and none of them is free:

- **Restart again.** It will land on offset `735233` and fail again. Auto-restart would repeat that cycle for him.
- **Skip this one record.** Stop the connector, move the consumer group forward to `735234`, and resume. The record stays in Kafka until retention removes it, but the sink won't write it to Postgres, so someone should keep a copy before moving on.
- **Change how the sink handles bad records.** Configure error tolerance and a [dead-letter queue](https://www.conduktor.io/glossary/dead-letter-queues-for-error-handling) so future incompatible records are set aside instead of stopping the pipeline. That's a broader change to the connector, and Bob doesn't have permission to make it.

He leans toward skipping the record to get reporting moving again. But first he wants to know whether it's a harmless test or real data that someone expects to see in Postgres. His assistant tries to look up the producer in Console's audit log and gets a permission error. Bob asks Priya to check.

## Priya Finds the Sender and Reviews the Fix

Priya can see the cluster-wide history Bob can't. She runs a custom agent task for this cluster, **Failing sink connector, find the poison pill**, which follows the failing connector back to the offending record and produces an approval request rather than making the change itself.

It confirms the same offset and format mismatch, then checks Console's audit log. There it finds a `Kafka.Topic.ProduceRecord` event on `pageviews` from `jack@conduktordemo.io`. What looked like a manually produced test record now has an identifiable sender.

The agent proposes a recovery plan: stop `postgres-sink`, create `pageviews.dlq`, copy the bad record there, advance `connect-postgres-sink` from `735233` to `735234` "and leave everything else as it is", resume the connector, and let Jack know what happened. It never proposes another restart. Its last step is for later: add error tolerance and a dead-letter queue to the connector, so the next bad record doesn't stop it.

Agentic

Home

Identities

Tasks

Models

Agents

Scheduled

Event-driven

Output

Reports

Recommendations

Approvals

Direct updates

Activity

** Connector action → recovery

** Failing sink connector, find the poison pill

Settings
main

Output / Failing sink connector, find the poison pill / ea6846c7-95c4-464d-be37-cb650f8a389f

Ask   A

Output

Everything your agents hand back, reports to read, recommendations to act on, approvals to decide, and a record of direct updates.

Reports Recommendations Approvals Direct updates

Search by title, task or agent Status Agent

Output Agent Status Produced****

Unblock postgres-sink: skip the plain-JSON record at pageviews/0@735233 Unblock postgres-sink: skip the plain-JSON record at pageviews/0@735233 Failing sink connector, find the poison pill Failing sink connector, find the poison pill Pending 9 minutes ago

Escalate postgres-sink: non-Avro records on pageviews, restarts not helping Escalate postgres-sink: non-Avro records on pageviews, restarts not helping Connector recovery Connector action → recovery Pending 12 minutes ago

Unblock postgres-sink: skip the plain-JSON record at pageviews/0@735233 Approval Failing sink connector, find the poison pill Pending Approved

Produced 9 minutes ago · agent Failing sink connector, find the poison pill

Reject Approve

Output Trace

Pending your decision: nothing has been applied

The agent wrote no changes. Approving records your decision for the steps below; a person carries them out.

Approved by admin@demo.dev

a few seconds ago Jack test record; copied to pageviews.dlq, Bob skipped it

Finding

**Connector:** postgres-sink (io.confluent.connect.jdbc.JdbcSinkConnector) on connect cluster local-connect reads topic pageviews. Its only task, task 0 on worker connect:8083, is FAILED.

**Error:** The task failed in the converter stage, before any transform ran and before anything was written to Postgres. This is not a credentials, network or database problem.

**Record:** Consumer group connect-postgres-sink is Empty. Its committed offset on pageviews partition 0 is 735233, the end offset is 745865, and lag is 10632. The record at partition 0, offset 735233 has:

- timestamp 2026-11-16T15:30:54.158Z
- an empty key
- plain JSON value {"viewtime":"yesterday","userid":"User_9","pageid":"Page_42"} (format Json, schemaId null, 61 bytes)
- header app_name=Conduktor

It has no Schema Registry magic byte or schema id, which is exactly why the AvroConverter rejects it. It is also wrong on content: subject pageviews-value (AVRO, id 3, version 1) expects viewtime to be a long, and this record has the string "yesterday".

**Previous record:** Offset 735232 (2026-11-16T15:30:54.093Z) is valid. Its key is 7339581, its format is AvroWithSchemaRegistry with Confluent schema id 3, it is 24 bytes, and viewtime is 7339581. It carries the datagen headers task.generation, task.id and current.iteration.

**Who produced it:** The audit log has one Kafka.Topic.ProduceRecord event on pageviews, by Console user **jack@conduktordemo.io** at 2026-11-16T15:30:54.100162Z. That is within about 60 ms of the record's timestamp, and the record's app_name=Conduktor header also points to a Console produce.

**Dead-letter topic:** pageviews.dlq does not exist (get-topic returned "Topic not found"), so it has to be created before the record can be copied there.

Proposed steps

- Stop connector `postgres-sink` on connect cluster `local-connect` (cluster `local-kafka-cluster`) so consumer group `connect-postgres-sink` stays inactive while you change its offset.
- Create topic `pageviews.dlq` on `local-kafka-cluster`; it does not exist yet.
- Copy the record at `pageviews` partition 0, offset 735233 to `pageviews.dlq` without changing it: empty key, value `{"viewtime":"yesterday","userid":"User_9","pageid":"Page_42"}`, header `app_name=Conduktor`. Add headers for the source coordinates (topic=pageviews, partition=0, offset=735233, timestamp=2026-11-16T15:30:54.158Z).
- Reset consumer group `connect-postgres-sink` on topic `pageviews` partition 0 from 735233 to 735234. Move this one offset only and leave everything else as it is.
- Resume `postgres-sink`. Confirm task 0 is RUNNING on `local-connect` and that the lag of `connect-postgres-sink` on `pageviews` partition 0 keeps falling from 10632. If the task fails again, inspect the record at the new committed offset before skipping anything more.
- Tell jack@conduktordemo.io and the team that owns `pageviews` that the plain-JSON record they produced through Console on 2026-11-16 at about 15:30:54Z (pageviews/0@735233, now copied to pageviews.dlq) stopped postgres-sink.
- To stop this happening again, add `errors.tolerance=all`, `errors.deadletterqueue.topic.name=pageviews.dlq` and `errors.deadletterqueue.context.headers.enable=true` to `postgres-sink`. As well or instead, reject records that have no valid Schema Registry schema id before they reach `pageviews`, for example by only allowing Avro produces with the schema registry serializer.

Approve this proposal?

Approving **Unblock postgres-sink: skip the plain-JSON record at pageviews/0@735233** records your decision. Nothing is executed. The steps the agent proposed are for someone to carry out.

Reason (optional)

  Kept with the approval, for whoever reads it later

Cancel Approve

*Priya opens the two approvals in her inbox, reads the poison-pill record and its sender, and reviews the proposed steps before approving them.*

Another built-in agent, **Unstable connectors**, sees the wider pattern: `postgres-sink` has failed and been restarted four times in the window, all by Bob. One agent explains why repeating the action won't help; the other shows that this is now a pattern worth investigating.

Bob stops the connector, and Priya creates `pageviews.dlq` and copies Jack's record into it before anyone moves the offset. Approving the card records her decision, and nothing on the cluster changes because she approved it. Bob can now recover his team's connector without losing track of what it skipped.

## Bob Skips One Record Instead of 735,000

With the record copied, Bob opens **Reset Offset** for `connect-postgres-sink`. The drawer initially shows **Earliest**. Its preview puts the offset at `0`.

That would be a very different recovery. Instead of skipping one record, the sink would replay roughly 735,000 earlier pageviews into Postgres. Depending on how the sink handles repeated writes, that could mean duplicates or a lot of unnecessary work.

Bob changes the option to **Shift by**, enters `1`, and checks the preview: partition 0 will move from `735233` to `735234`. He presses **Reset**, then **Resume**. This time the task stays running, and consumer lag drops from `19,616` to `916` in about a minute and a half.

Console

Home

Topics

Schema registry

Consumer groups

Kafka Connect

Service accounts

Analytics

Insights

Governance

Application Catalog

Topic Catalog

Resource policies

Data quality

Settings
main

 Local Kafka local-kafka-cluster  Consumer Groups / connect-postgres-sink Kafka Connect / Local Connect / postgres-sink

Search⌘K   BB

connect-postgres-sink

State Empty  Consume rate**0 msg/s** Offset lag**13,239 18,760** Time lag**10m 49s 15m 19s**

Add label

Topics1 Members0 Alerts0 Graphs

**Offset lag**1H 1D 7D 30D Alerts *(0)*

16k 14k 12k 10k 8k 6k 4k 2k 0

18k 16k 14k 12k 10k 8k 6k 4k 2k 0

12:00 15:00 18:00 21:00 00:00 03:00 06:00 09:00

**Time lag**1H 1D 7D 30D Alerts *(0)*

15m 10m 5m 0

12:00 15:00 18:00 21:00 00:00 03:00 06:00 09:00

Search by any field   1-1 of 1    Display

Topics Consume rate Offset lag Time lag

pageviews 0*msg/s* 13,239 18,759 10m 49s 15m 19s

Reset Offset Duplicate  Delete

postgres-sink

Status Stopped Running  Type **JdbcSinkConnector** Auto-restart**Disabled** Topics**1**

Add label

Overview Configuration Offsets Auto-restart Alerts0

**Failed tasks (Last 24hrs)**Alerts *(0)*

4 3 2 1

11 12 13 14 15 16 17 18 19 20 21 22 23 00 01 02 03 04 05 06 07 08 09 10

**Failed tasks (Last 90 days)**Alerts *(0)*

Mon*****************************1*Tue******************************Wed******************************Thu******************************Fri******************************Sat******************************Sun*******************************September**October**November*

Search by name

Task ID Worker State

**No task found**Try adjusting your search criteria

Reset Offset

Topics

All topics

Pick a strategy

Earliest Shift by

Earliest Latest Specific offset Shift by Datetime

Preview

Topic Partition Offsets Current Offsets New Offsets

pageviews 0 *0 - 749230**0 - 753890* 735233 *0**735234*

Reset form Reset

Offset successfully refreshed

Connector postgres-sink has been resumed successfully

Agentic

Home

Identities

Tasks

Models

Agents

Scheduled

Event-driven

Output

Reports

Recommendations

Approvals

Direct updates

Settings
main

Output / Offset reset → business impact / 96fb4939-559b-4d17-85e9-2f26217d1274

Ask   A

Output

Everything your agents hand back, reports to read, recommendations to act on, approvals to decide, and a record of direct updates.

Reports Recommendations Approvals Direct updates

Search by title, task or agent Agent

Output Agent Produced****

connect-postgres-sink moved forward 1 offset on pageviews: 1 record skipped, likely a deliberate poison-pill skip Offset reset impact Offset reset → business impact a few seconds ago

connect-postgres-sink moved forward 1 offset on pageviews: 1 record skipped, likely a deliberate poison-pill skip Recommendation Offset reset impact Open

Produced a few seconds ago · agent Offset reset → business impact

Dismiss Mark as actioned

Output Trace

**A suggestion, not a change**Nothing happens unless you act on it. Dismissing it is a valid answer.

Finding

**What happened.** At 2026-11-16T15:46:34Z, bob@conduktordemo.io reset consumer group connect-postgres-sink with a ShiftBy n=1 reset on all of its topics.

**How much was skipped or replayed.** Shifting by +1 on one partition moves the position forward, so **exactly 1 record was skipped**. Nothing will be replayed.

**Why it was likely done.** Bob's audit trail shows a typical poison-pill troubleshooting sequence on the postgres-sink connector (on local-connect): two connector restarts at 15:31 and 15:32 (through his bob-editor token), two task restarts at 15:35 and 15:36, a **Stop** at 15:41, then the +1 offset shift at 15:46. The reset looks deliberate, meant to step over one record the sink couldn't process.

**Business impact.** pageviews is clickstream data (about 754k messages, 7-day retention, 3 consumer groups). One missing pageview in Postgres slightly undercounts analytics.

*Bob checks the reset preview, shifts forward by one offset, and resumes the sink; an agent then reviews what changed.*

The reset triggers another custom agent, **Offset reset impact**. It reconstructs the sequence from Console's audit log, from Bob's restarts to the stop and the reset. Its finding is specific: `connect-postgres-sink` moved forward one offset on `pageviews`, so one record was skipped. It also sizes the damage: one missing pageview in Postgres slightly undercounts the reporting data.

Bob has a working connector. Priya has a preserved copy of the record, an identified sender, and an auditable account of why the offset moved.

## The Connector Is Running. The Next Bad Record Is Still a Decision.

Bob diagnosed the failure from his own terminal and made the one-offset change his role allows. Priya used broader visibility to confirm who sent the record and approve a recovery that kept a copy. The agents noticed the repeated failure, proposed the steps, and explained the impact afterward. **A person made every change.**

Here's where each piece helped:

| Piece | What it does | Where it showed up |
|---|---|---|
| **Conduktor MCP server** | Gives an AI assistant Console's tools within the user's permissions | Bob finds offset `735233`, but can't read the audit log |
| **Connector recovery** (built in) | Reacts to connector actions and escalates when retrying won't help | Each restart leads to an escalation instead of another restart |
| **Unstable connectors** (built in) | Reviews failing and repeatedly restarted connectors on a schedule | Priya sees the four restarts as one pattern |
| **Failing sink connector, find the poison pill** (custom) | Finds the offending record, checks its origin, and proposes steps for approval | Priya gets Jack's audit event and the recovery plan |
| **Offset reset impact** (custom) | Reviews consumer-group resets and estimates their effect | The one-record skip is recorded and explained |

There's still a choice for the next failure. Creating `pageviews.dlq` and copying this record into it preserved evidence; it **didn't** configure `postgres-sink` to send future failures there automatically. Priya could make that separate configuration change, using error tolerance and dead-letter-queue settings so malformed records don't stop reporting again. Or she could keep the sink strict and prevent records like Jack's from reaching the topic in the first place. For clients producing through Conduktor Gateway, the [Schema ID required](https://docs.conduktor.io/guide/use-cases/apply-traffic-control-policies#topic-required-schema-id-policy) policy is one way to enforce that.

Either way, the agents didn't silently discard a bad record or decide the team's data-loss policy. They gave Bob and Priya the context to make a deliberate one-record exception, get the pipeline moving, and see exactly what changed.

## See It Live on 8 December

Register for our webinar on Tuesday, 8 December, at 11:00 AM ET / 8:00 AM PT to see Conduktor Agents work through connector failures like this one live: [Leave the Chores to Kafka Agents](https://www.conduktor.io/events/webinars/conduktor-agents-live?src=blog-recovering-a-kafka-connector-from-a-poison-pill). Can't make it? Register anyway and we'll send you the recording.

---

Related: [Investigating a Leaked Kafka Credential with Conduktor Agents →](https://www.conduktor.io/blog/investigating-a-leaked-kafka-credential) · [Introducing Conduktor Agents →](https://www.conduktor.io/blog/conduktor-agents) · [Conduktor MCP + Skills for AI Agents →](https://www.conduktor.io/blog/conduktor-mcp-and-skills-for-ai-agents) · [Bounce Bad Kafka Data with JSON Schema Rules →](https://www.conduktor.io/blog/bounce-bad-kafka-data-with-json-schema-rules)
