In odoo 18 when there is a timeout on the db connection, the cron thread dies out completely. It does not respawn, without restarting odoo itself completely. We're running it in a container. We would expect that this temporary error, which most likely stems from the backup that is running at the time when we noticed this error multiple times, does not crash the whole thread permanently. Instead we would expect the thread to restart instead.

```

Traceback (most recent call last):

  File "/opt/bitnami/python/lib/python3.12/threading.py", line 1075, in _bootstrap_inner

    self.run()

  File "/opt/bitnami/python/lib/python3.12/ threading.py", line 1012, in run

    self._target(*self._args, **self._kwargs)

  File "/opt/bitnami/odoo/lib/odoo-18.0.post20241205-py3.12.egg/odoo/service/server.py", line 496, in target

    self.cron_thread(i)

  File "/opt/bitnami/odoo/lib/odoo-18.0.post20241205-py3.12.egg/odoo/service/server.py", line 468, in cron_thread

    pg_conn.poll()

psycopg2.OperationalError: could not receive data from server: Connection timed out

```

Is there some workaround we could apply? And how can we report such things in the right way so they get addressed and fixed?