Repository navigation
Replies: 9 comments 4 replies
|
Conductor ver1.0.18 |
|
How interesting! There are no known issues with daylight savings time. In fact, we have an official recipe for targeting jobs that run during the "danger hour" (the hour that gets duplicated or skipped depending on the changeover direction). Can you provide more details about your setup? I'm curious to learn exactly how your job is scheduled (are you using "Catch-Up" mode by any chance?), and what your upcoming jobs table looks like. That table is constructed literally by advancing an epoch time counter minute by minute and seeing which jobs would run. |
|
FYI, I just installed version 1.0.20 and upgraded all satellites to 1.0.12 My setup: LXC container on Proxmox, Ubuntu, xyOps conductor managed via control.sh and @reboot cron (not systemd). System timezone is America/Denver, confirmed correct post-DST changeover via timedatectl. The "timezone": "" field in config.json is empty. The payroll jobs are scheduled as simple timed events — I'm not using Catch-Up mode. What I observed this morning was that the upcoming jobs table was showing the job due to run near the 8am hour instead of 7am, even though the schedule is set to 7am. The job did eventually run and completed successfully. My question: since "timezone": "" is empty in config.json, is xyOps falling back to the system timezone for schedule evaluation, or does it require an explicit value in that field? If it requires an explicit value and defaults to UTC when empty, that would explain a one-hour drift after a DST changeover. Should I set "timezone": "America/Denver" there?
Thanks, |
|
Ah ha, well I can explain at least one of the issues! The Interval Trigger is purely seconds-based, in a very "raw" sense. What I mean is, that "14 Days" is really just interpreted literally as "1,209,600 seconds" under the hood (i.e. So really it's just counting the raw seconds between each job run. It isn't "daylight savings time aware". Unfortunately, that would be a really difficult thing to implement. The only options I can see are:
|
|
Biweekly payroll, so our only real option interval. OK, I will write a script to shift interval triggers by 3600 seconds based on spring or fall DST. Not the end of the world. It's just funny that I have to write automations for my automations:) Thanks for the background on Timezones. I will fix accordingly. |
|
Fully implemented in xyOps v1.0.21! 😃 New scheduler modifier trigger has been added: Every Nth For your case, since you need it to run every 14 days (every other week), you can schedule the job to run weekly on the weekday you need (e.g. Monday), then add a "Every Nth" modifier set to 2:
This will skip every other Monday run, but still honor the exact time of day you set, and timezone / daylight savings, etc. To control "which" Monday it starts on, you can reset the internal state counter. Set it to As another example, if you needed it to run every N days that isn't linked to a weekday, for e.g. every 8 days, then you can set it to run daily, then set the Every Nth to 8. Hope this helps! |
|
This is perfect. Now I can remove my automation for my automations :) Unbeilveable! Did I tell you I love xyOps 🥇 :) Thank you, |
|
You helped us move away from two subscriptions.
RemoteLink (automation) >>> https://www.unwiredremotelink.com/
and
Checkmk >>> https://checkmk.com/
While xyOps Honeycomb still needs refinement it is infinitely better than Checkmk because xyOps is the foundation.
RemoteLink never would entertain adding bi-weekly in their scheduler. I had to use a windows scheduler to inject an SQL query to do it. I only showed you there was a desire and boom!
So I was already eager to donate. More to come…
Thank you,
Dave
From: Joseph Huckaby ***@***.***>
Sent: Tuesday, March 10, 2026 1:51 PM
To: pixlcore/xyops ***@***.***>
Cc: cju-mt ***@***.***>; Mention ***@***.***>
Subject: Re: [pixlcore/xyops] Daylight savings time issue? (Discussion #185)
@cju-mt<https://github.com/cju-mt> WOW! That was fast! Thank you so much for the sponsorship! You are sponsor number one! 😃 ❤️
—
Reply to this email directly, view it on GitHub<#185 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC2ANZ7TSACGKC2UH4E2BNT4QBW37AVCNFSM6AAAAACWMAZGSOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGM3DGMA>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|




Uh oh!
There was an error while loading. Please reload this page.
Has anyone else had an issue after daylight savings time? I have a scheduled job that normally runs at 7:00 AM however this morning I look and they had not run yet but under upcoming jobs was two different jobs scheduled to run at 7:00 AM but it was coming up on 8:00 AM when it was going to run the jobs. I looked at the events they are scheduled for 7:00 AM. I checked the time on the server and it is correct, set to mdt and it matched the time that xyOps displays up in the upper right corner.
"does restarting the conductor correct DST drift on scheduled jobs, or do jobs need to be manually re-saved?"
Since I haven't seen a ton of posts on this I'm assuming no one else ran into it.
Lucky me :)
All reactions