Module is incompatible with Drupal Configuration Sync processes

I can also reproduce this issue. I fixed it by recreating the ultimate cron tables.

Still unable to reproduce this. The module just implements hook_schema() like many other modules.

I had the same issue with a multi-site Drupal 10.1.8
Site1 was fine
Site2: After updated and cim, it was showing the similar message as in #5
As mentioned in previous comments, only known solution was to create tables manually.

drush --uri= sql-query "CREATE TABLE ultimate_cron_log ( lid varchar(176) NOT NULL COMMENT 'Lock ID', name varchar(166) NOT NULL COMMENT 'Name', log_type int(11) NOT NULL DEFAULT '0' COMMENT 'Log type', start_time double NOT NULL DEFAULT '0' COMMENT 'Timestamp of execution start', end_time double NOT NULL DEFAULT '0' COMMENT 'Timestamp of execution end', uid int(11) NOT NULL DEFAULT '0' COMMENT 'User ID', init_message text COMMENT 'Initial message', message text COMMENT 'Message', severity int(11) DEFAULT '-1' COMMENT 'Max severity level of the execution', PRIMARY KEY (lid), KEY idx_last (name(80),start_time,end_time,log_type)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Logs'"

drush --uri= sql-query "CREATE TABLE ultimate_cron_lock ( lid bigint(20) NOT NULL AUTO_INCREMENT COMMENT 'Lock ID', name varchar(166) NOT NULL COMMENT 'Name', current bigint(20) NOT NULL DEFAULT 0 COMMENT 'Current lock', expire double NOT NULL DEFAULT 0 COMMENT 'Expiration time of lock', PRIMARY KEY (lid), UNIQUE KEY idx_name (name,current)\n) ENGINE=InnoDB AUTO_INCREMENT=2241728 DEFAULT CHARSET=utf8mb4 COMMENT='Locks'"

drush --uri= sql-query "CREATE TABLE ultimate_cron_signal ( job_name varchar(166) NOT NULL COMMENT 'Name of job', signal_name varchar(166) NOT NULL COMMENT 'Name of signal', claimed tinyint(4) NOT NULL DEFAULT 0 COMMENT 'Is signal claimed', PRIMARY KEY (job_name,signal_name)\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Signals'"