Scheduling option issue: Super not launching at selected time

[I-Wildcard]

Hello team,

I was testing the Super 5 scheduling option today when updating to macOS Sequoia 15.1, and for some reason Super did not launch at the time I selected (17.30).
I did receive the reminders 4 hours and 15 minutes before the selected time (as per our customisation), which worked great - but when 17.30 arrived nothing happened.

I looked into the logs, and this is what I see:

Tue Oct 29 17:15:06 Hostname super-starter[45989]: **** S.U.P.E.R.M.A.N. 5.0.0 - LAUNCHDAEMON ****
Tue Oct 29 17:15:07 Hostname super[46004]: **** S.U.P.E.R.M.A.N. 5.0.0 - SUPER STARTUP ****
Tue Oct 29 17:15:08 Hostname super[46004]: Status: Mac computer with Apple silicon running: macOS Sequoia 15.0.1-24A348
Tue Oct 29 17:15:08 Hostname super[46004]: Status: Last macOS startup was: 2024-10-17:10:46:08
Tue Oct 29 17:15:09 Hostname super[46004]: Status: Current active GUI user is: username (502)
Tue Oct 29 17:15:15 Hostname super[46004]: Status: Managed by Jamf Pro 11.10.1 hosted at: https://company.jamfcloud.com/
Tue Oct 29 17:15:15 Hostname super[46004]: Parameter Warning: The --display-notifications-centered type of DIALOG is ignored because dialogs are not notifcations.
Tue Oct 29 17:15:16 Hostname super[46004]: Status: Previously scheduled installation workflow active for: 2024-10-29:17:30
Tue Oct 29 17:15:16 Hostname super[46004]: Status: macOS update/upgrade workflows automatically authenticated via saved password for current user: username
Tue Oct 29 17:15:16 Hostname super[46004]: **** S.U.P.E.R.M.A.N. 5.0.0 - CHECK FOR SOFTWARE UPDATES/UPGRADES ****
Tue Oct 29 17:15:16 Hostname super[46004]: Status: Restrictions configuration profile is deferring macOS major upgrades for 90 days.
Tue Oct 29 17:15:17 Hostname super[46004]: Target: macOS minor update macOS Sequoia 15.1-24B83 which is a 3GB download.
Tue Oct 29 17:15:17 Hostname super[46004]: Status: Previously set automatic zero date based on the macOS Sequoia 15.1-24B83 workflow start date of 2024-10-29:09:32.
Tue Oct 29 17:15:17 Hostname super[46004]: Status: Scheduled installation date of 2024-10-29:17:30 has not passed and the user can reschedule.
Tue Oct 29 17:15:17 Hostname super[46004]: **** S.U.P.E.R.M.A.N. 5.0.0 - SCHEDULED RESTART macOS Sequoia 15.1-24B83 MINOR UPDATE VIA SOFTWAREUPDATE ****
Tue Oct 29 17:15:17 Hostname super[46004]: Status: Scheduled installation reminder of 240 minutes prior to installation has passed.
Tue Oct 29 17:15:17 Hostname super[46004]: Status: Scheduled installation reminder of 15 minutes prior to installation has passed.
Tue Oct 29 17:15:17 Hostname super[46004]: Status: Focus days deadline of 2024-11-05 (7 day(s) after 2024-10-29:09:32) not passed.
Tue Oct 29 17:15:17 Hostname super[46004]: Status: Soft days deadline of 2024-11-08 (10 day(s) after 2024-10-29:09:32) not passed.
Tue Oct 29 17:15:17 Hostname super[46004]: IBM Notifier: Scheduled installation warning dialog (this dialog has no timeout).
Tue Oct 29 17:15:17 Hostname super[46004]: Exit: super is scheduled to automatically relaunch at: 2024-10-29:18:15:00
Tue Oct 29 17:15:17 Hostname super[46004]: **** S.U.P.E.R.M.A.N. 5.0.0 - EXIT CLEAN ****

Super is saying that it'll automatically relaunch at 18.15 and not at 17.30.
I encountered this issue on two different devices.

Let me know if you need additional information.

Thank you!

[ofirgalcon]

+1

[Macjutsu]

Yeah... sorry... I'd have to see a --verbose-mode log to figure out why super is not properly setting a relaunch time.

[I-Wildcard]

Hi,

I was able to replicate the issue on another Mac.

Scheduled date: 17.00
After dismissing the second reminder (15 minutes before the scheduled date), the next autolaunch date I see is set to 17.56 and not at 17.00 as expected.

Attached --verbose-mode logs:
Super.log

[rocketman8080]

Hi, I think I have a related issue where super does not auto-relaunch after deferral.

snippet of log is below, - the script does not re-launch at the specified time post deferral. How is the re-launch controlled?
May be a dumb question, but is the script running as a daemon in the background, or is scheduled to run periodically via cron-like mechanism? thank you,

Sat Nov 09 13:28:15 MacMini super.sh[27440]: Exit: super is scheduled to automatically relaunch at: 2024-11-09:14:28:00
Sat Nov 09 13:28:15 MacMini super.sh[27440]: Verbose Mode: Function exit_clean: Line 4160: Local preference file at clean exit: /Library/Management/super/com.macjutsu.super:
{
    DeferralRestrictionsCache = 0;
    DeferralRestrictionsChecksum = 0;
    DisplayIconDarkFileCachedOrigin = DEFAULT;
    DisplayIconLightFileCachedOrigin = DEFAULT;
    MDMClientAvailableCache = 1;
    MDMClientListChecksum = e2081d00fcdc53395538128b68c959fb;
    MSUListChecksum = e867b323b5e81a152498b12be2e00e9d;
    MacLastStartup = "2024-11-07:11:58:29";
    MacOSBetaProgramCache = 0;
    MacOSMSULabelDownloaded = "macOS Sequoia 15.1-24B83";
    MacOSMSULastStartupDownloaded = "2024-11-07:11:58:29";
    NextAutoLaunch = "2024-11-09:14:28:00";
    ScheduleZeroDateAutomaticStart = "2024-11-07:11:52";
    SuperStatus = "Sat Nov 09 13:28:15: Pending: User chose to defer, setting a deferral of 60 minutes.";
    VerboseMode = 1;
    WorkflowTarget = "macOS Sequoia 15.1-24B83";
}
Sat Nov 09 13:28:15 MacMini super.sh[27440]: **** S.U.P.E.R.M.A.N. 5.0.0 - EXIT CLEAN ****

[Brandon-Muller]

+1
A thread was started in the MacAdmin Slack about this issue too.

[gockmana]

super.log
I'm experiencing the same issue across multiple computers whether trying to upgrade from macOS Sonoma to Sequoia or to keep macOS Sequoia up to date. I've tested the same computer multiple times and attached the full log for reference. The most recent test was done in verbose mode.

[TechTrekkie]

Just adding to this thread, I'm seeing the same issue. I'll try to get a verbose log, but In the latest example, I scheduled an install for 01/14/25 at 2:00 PM, log shows that as the scheduled install date, but it set the NextAutoLaunch for 01/15/25 at 5:09 AM

[TechTrekkie]

got a verbose log example with the issue. Scheduled an update for 2025-01-15:15:00 and the NextAutoLaunch is set for 2025-01-16:04:52:00 preventing it from running at the scheduled time.
I can see further up the log a line that shows
Wed Jan 15 12:32:10 ZG16338 super[96667]: Status: Scheduled installation on WED 2025-01-15:15:00, deferring for 980 minutes from now.
but it should have only deferred for about 148 minutes, not 980.

super 3.log

[TechTrekkie]

I believe I may have figured out the issue and a solution.

in the #super script, Line 5360 , the calculation for determining the deferral_timer_scheduled_install_minutes is workflow_scheduled_install_epoch - workflow_time_epoch) / 60
I believe the problem is that the workflow_time_epoch appears to get set at the beginning of the runtime. If the restart dialog is displayed for a user for a long period of time because they are either away or choose to ignore it, the time between those two epoch's grows, inflating the calculation.

I added workflow_time_epoch=$(date +%s) above that line to set it to the current time as a test, and that appears to calculate the proper deferral minutes for a scheduled restart.
I'm doing some additional testing but so far this looks to be the problem/solution.