The policy executes a little after the time it is scheduled to run, however the next cron time is set with respect to the created time and not the executed time. So setting the cooldown to 61 seconds itself will make this policy never trigger right?