DST time change causes Scheduled Aggregations to run at different times

The UI for Scheduled Aggregation shows the times for which you want to run the jobs. But during DST, the time offset gets applied and causes the jobs to run an hour earlier, then adjusts back when DST is OFF.

This causes issues on our aggregations running off so we need to keep manually adjusting it during DST time change. Anybody else having this issue? Thanks!

:bangbang: Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.

I submitted an idea for this in case this also impacts you: https://ideas.sailpoint.com/ideas/GOV-I-3974

The timezone behaviour is borderline schizophrenic across the tenant instance, IMO:

…and why “VA cluster time zones do not observe DST”…no idea. Maybe SailPoint is rooting for DST to go away in North America at some point.

Voted in the idea. Thanks.

1 Like

Hi @rtatco,

You can set the timezone in Virtual Appliance cluster and going forward your scheduled aggregations in UI will follow that timezone. So in future, you won’t need to change timings when DST are OFF and ON.

Thanks,
Favaz

…but SailPoint’s documentation (linked above) mentioned:
“VA cluster time zones do not observe daylight savings time.”

Unless you’re suggesting him to, say, change timezone from PST to PDT (and vice-versa)…which is essentially like toggling DST. The cluster, ideally, should be self-aware of this. Just like a modern day smartphone in everyone’s pocket these days. Why can’t the cluster do this?