Looks like the problem is fairly isolated in common/CommonUtils.vala:
in next_run_date(), it always returns the return of most_recent_scheduled_date(), or if comparing to last_run returns a negative timespan, then it adds the configured period.
Turns out that most_recent_scheduled date always returns a DateTime at 00:00Z due to the way it's computed.
Looks like the problem is fairly isolated in common/ CommonUtils. vala:
in next_run_date(), it always returns the return of most_recent_ scheduled_ date(), or if comparing to last_run returns a negative timespan, then it adds the configured period.
Turns out that most_recent_ scheduled date always returns a DateTime at 00:00Z due to the way it's computed.