Dynflow relies heavily on database (and redis with sidekiq deployments) being available all the time. It should be able to withstand minor connectivity drops.

Prompted by https://community.theforeman.org/t/dynaflow-orchestator-will-not-become-active/44926/3

This will be more important as we containerize because we should no longer rely on the installer restarting DynFlow after a PostgreSQL restart, as we currently do (https://github.com/theforeman/puppet-foreman/blob/915cd91cc40c8507f87f224d666794247713d794/manifests/dynflow/worker.pp#L55 since https://github.com/theforeman/puppet-foreman/commit/f44d723eab55484cdd35bb7acc3f5aee0db346e7).