My Rundeck detail
One-time scheduled job executions continue after rundeck server restart.
One-time scheduled job executions are still present after a rundeck server restart, however they don't continue and thus are not executed
How to reproduce Behavior
@shoelzle Can you check if there are any errors in your service.log?
Fyi, I have the same problem. It started on the update to 2.6.10.
Is this scheduled jobs, as in using a fixed crontab schedule, or a one-off ad hoc scheduled job (using 'Run Job Later')?
@jamieps , this only happens with one-off ad-hoc scheduled jobs. I'll clarify this in the issue description.
@jamieps , I'll check the logs in a few days.
Does your job have secure input options? Those cannot be rescheduled automatically at startup (currently), if so it should log a warning to that effect.