Bug: cron checks are executed on backend startup regardless of schedule about sensu-go HOT 2 CLOSED

A few quick notes regarding reproducing this:

• this only affects round-robin checks, interval and cron, when the Postgres config has enable_round_robin: true
• no need to restart the backend: simply updating a check to round-robin: true triggers the execution
• round-robin interval checks exhibit the same, but it's less clear whether or not this is incorrect
• when enable_round_robin: false, round-robin interval checks don't get restarted so there are small differences between etcd RR and Postgres RR ; unclear what's "correct" here

from sensu-go.

Unfortunately this problem is a design flaw. It would require an external central queue such as rabbitmq to alleviate, with agents connecting directly to it. We can't fix this in the 6.x version of Sensu.

from sensu-go.