# Connect fails to register a schema, how can I see what it tried to register?

**URL:** https://forum.confluent.io/t/connect-fails-to-register-a-schema-how-can-i-see-what-it-tried-to-register/3093
**Category:** Kafka Connect
**Created:** [14 October 2021 16:18 UTC](https://forum.confluent.io/t/connect-fails-to-register-a-schema-how-can-i-see-what-it-tried-to-register/3093 "2021-10-14T16:18:55Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![cannontrodder](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/cannontrodder/32/191_2.png) [@cannontrodder](https://forum.confluent.io/u/cannontrodder)
#### Post date: [14 October 2021 16:18 UTC](https://forum.confluent.io/t/connect-fails-to-register-a-schema-how-can-i-see-what-it-tried-to-register/3093/1 "2021-10-14T16:18:55Z")

</div>

Connect is giving me the error: “Schema being registered is incompatible with an earlier schema for subject” . I know what the registered schema is by querying the Schema Registry API but I just need to find out exactly what schema Connect is trying (and failing) to register. Problem is, when I set Connect to trace level logging I don’t actually see what it tried to register with Schema Registry.

I did a PUT to /admin/loggers/root and passed in {“level”: “TRACE”} - should I not have seen the request to Schema Registry in there?

Can anyone suggest any strategies for finding out the specific schema it is failing to register so I can work out if I can change it?

I’m using strimzi 0.25 which deploys the connect image compatible with kafka-2.8.0

(I am sorely tempted to disable the schema checking on this topic but that feels like defeat…)

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex019/uploads/confluentcommunity/original/1X/c49438c90c9df282e9996fdf6971be890c71b65a.svg) [@system](https://forum.confluent.io/u/system)
#### Post date: [13 November 2021 16:19 UTC](https://forum.confluent.io/t/connect-fails-to-register-a-schema-how-can-i-see-what-it-tried-to-register/3093/2 "2021-11-13T16:19:46Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
