An event contract describes the business identity, meaning and evolution of a record. A stable key can keep one entity's history in a partition, while an event ID supports deduplication and a sequence helps detect gaps. Those fields solve different problems. A random key per event can distribute traffic but sacrifices the expected per-entity ordering. A single constant key preserves one partition's order while creating a bottleneck. These decision tasks ask for a design that balances the stated ordering and parallelism requirements. Choose the key from the business entity, then say what evidence detects missing or repeated lifecycle events. The broker cannot infer those business rules from payload text.
Inspect the topics, partition logs and group offsets before changing the cluster.