Timeouts on some topics when using confluent cli

Hi team,

I’m using the schema deletion tool to find and delete unused schemas. When I do a scan (confluent schema-registry cleanup --all) it starts getting the schemas and scanning the topics. After 5 minutes scanning topics, I start seeing the following 1 minute timeouts more and more often, until it’s only timeouts and the command fails (I assume because these are the largest topics):

FAIL|rdkafka#consumer-34| [thrd:GroupCoordinator]: GroupCoordinator: lkc-XXXXXXX.us-east-1.aws.glb.confluent.cloud:9092: Disconnected (after 59996ms in state UP, 1 identical error(s) suppressed)

|FAIL|rdkafka#consumer-48| [thrd:GroupCoordinator]: GroupCoordinator: lkc-XXXXX.eu-west-1.aws.glb.confluent.cloud:9092: Disconnected (after 59992ms in state UP, 1 identical error(s) suppressed)

I think it may be a 1 minute timeout being hit for large topics. Is there any setting that can be modified to increase such timeout, either in the brokers, the confluent CLI, or the schema deletion tool CLI plugin?

Thanks in advance for the help.