Scheduled nightly reboot: use recurring Reboot API command — not a Blueprint or provisioning setting

Android

Learn how to set up scheduled nightly reboots for your managed devices using the Esper API. Scheduled reboots are not available as a Blueprint or provisioning setting—they must be configured separately through the API.

Before you begin

Scheduled reboots require:

• Devices running the Esper Esper Agent and online during the scheduled window
• Access to the Esper API (via the Esper Console or Developer Dashboard)
• Device ID or device group ID for targeting

Important: Scheduled reboot commands do not persist if a device is re-provisioned or its Blueprint is reapplied. You must reapply the API schedule separately after any provisioning changes.

Why scheduled reboots aren't in Blueprints

Blueprints manage static device configuration (kiosk mode, network settings, Apps & Configuration, permissions). Scheduled reboots are runtime operational commands, not configuration states. They require a scheduling mechanism that only the Esper API provides.

Schedule a recurring reboot via the Esper API

1. Open the Esper Console API or the Esper Developer Dashboard.
2. Locate the Reboot command endpoint.
3. Target your devices:
   • Target a single device using its device ID, or
   • Target a device group using its group ID
4. Configure the recurrence as nightly.
5. Choose your time zone:
   • Device local time (recommended if devices span multiple time zones), or
   • Console time (UTC-based Esper account time)
6. Select a low-activity window (for example, 02:00–03:00 local time) when devices are not actively in use. Use a short window to minimize timing drift.
7. Submit the API request.

Verify the scheduled reboot

1. In the Esper Console, navigate to Devices & Groups → [Device Name] → Commands.
2. Confirm the scheduled command appears with status Scheduled.
3. After the first execution window, verify the status changes to Success.
4. Check the device's last-seen and last-reboot timestamps to confirm the restart occurred.

Troubleshoot if the reboot didn't execute

Command shows as Queued or Failed:

1. Navigate to Devices & Groups → [Device Name] → Activity.
2. Check the Activity Feed for the scheduled time window to verify the device was online.

Device was online but the command didn't execute:

1. Check the installed Esper Esper Agent version on the device.
2. Ensure it meets the minimum version required for scheduled command support.
3. If the device was confirmed online and the command still did not run, contact Esper Support with the device ID, Esper Agent version, and command execution logs.

Device was offline during the scheduled window:

Esper does not queue the reboot for later execution. Devices that miss the window must wait for the next scheduled reboot time. Ensure devices are powered on and connected to the internet during your chosen window.

Important limitations

• Scheduled reboot commands are not Blueprint settings and will not persist after device re-provisioning.
• Devices offline for the entire scheduled window will miss the reboot command.
• Scheduling granularity and recurrence options depend on your Esper API version. Consult the current API documentation for supported parameters.
• OEM-locked devices with restricted reboot APIs may behave differently.

Still need help?

If you're unable to schedule a recurring reboot or the command isn't executing as expected, submit a support ticket. Include your device ID, Esper Agent version, the scheduled time window, and any relevant command execution logs.