This problem has existed ever since #2507031: Optimize automatic cron subscriber by moving automatic cron to a module → .
\Drupal\automated_cron\EventSubscriber\AutomatedCron::onTerminate() also gets invoked when visiting update.php, which may result in values getting set that the updates to be applied would have generated (e.g. renaming key-value pairs). This means that this can trigger a race condition that can cause updates to fail.
Update automatic_updates to have automatic_updates_update_9001() applied on a site that has automated_cron installed.
Ensure that \Drupal\automated_cron\EventSubscriber\AutomatedCron::onTerminate() does not run when visiting update.php.
TBD
Active
10.1 ✨
It denotes an issue that prevents porting of a contributed project to the stable version of Drupal due to missing APIs, regressions, and so on.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
As a workaround until this is resolved, I've added new maint commands to Drush so you can now setup con with drush maint:status && drush core:cron. This will avoid running cron while maint mode is disabled. That helps avoid deployment errors as discussed at https://drupal.slack.com/archives/C45SW3FLM/p1676470699500779?thread_ts=.... Drush PR is https://github.com/drush-ops/drush/pull/5380