Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Scheduling Recurring Orchestration Plans with an Interval
-
I'm having a problem getting a recurring orchestration plan to schedule correctly if it has an interval. As soon as the plan and schedule is created the job will immediately start and then occur at the interval from the time of this start instead of waiting for the start time defined by the schedule.
I did update to 1.6 today, but this has been an ongoing problem.
Any known issues about this already? I believe I've seen this fixed in the past, but maybe it was only for configuration jobs? Thanks!
Product: Otter
Version: 1.6.0
-
Hello Travis,
I was able to reproduce the bug. Otter sees the scheduled job with no "last run" date assigned to it and assumes that it's past the time the job is supposed to run. I'm discussing how to fix this with the team.
I think the fix in the past was for non-recurring scheduled jobs.
As a workaround, creating a recurring job with a plan that doesn't do anything, letting it run, and then editing the job to use the correct plan should work.
-
Sounds good. Thanks for taking a look Ben.
