Scheduler freezes when the database connection is interupted

[ghbm-itk]

Whenever an error happens in the database connection Scheduler stops.

It should be possible for it to automatically reconnect

[ghbm-itk]

The problem happens because of the way the update loop in Scheduler is set up.

Now instead of running on a continous loop, it runs once and then schedules a new loop afterwards. This is done to avoid overlapping loops in case a loop is slow.

Error handling needs to take this into account to ensure a new loop is scheduled even when connectivity issues happens.