@Manohar Babu

This error almost always means Pega couldn’t register or find the Avro schema in your Schema Registry, not that Kafka itself is down. First, verify network and auth: from the Pega node, curl the Schema Registry URL (/subjects) and confirm TLS truststore, basic auth/API key, and proxy settings are correct. Check your Kafka data set/stream config: use the exact Schema Registry URL, correct key/value serializers (Confluent Avro), and enable auto-register only if your SR user has write; otherwise pre-register the schema and reference its ID. Validate the Avro schema itself: include a proper name and namespace, ensure every optional field is a union with null first, and match Pega property types (no string vs number mismatches; map DateTime via logical types if used). Make sure the subject naming strategy matches what Pega/your serializers expect (TopicNameStrategy vs RecordNameStrategy); a mismatch causes “register” failures with odd error codes. Confirm compatibility mode (e.g., BACKWARD) and that your new schema evolves correctly from any existing subject version. If you see “error code: 0” with null message, it’s often permissions or SSL—try manual POST of the schema to the subject to surface the real error. Also ensure your Confluent client jars match the Schema Registry version; version drift can produce this exception. After fixing auth/URL and schema shape, restart the listener/publisher and test with a tiny message that exercises just the required fields.