Every managed device fleet has a set of tasks that need to happen on a regular basis. Devices need to be rebooted to clear accumulated memory and maintain performance. Configuration pushes need to be verified after updates. Content updates need to go live at specific times without requiring someone to manually initiate them at the delivery moment. Each of these tasks is straightforward in isolation, but across a fleet of hundreds of devices, the cumulative manual overhead of initiating them individually or monitoring them one at a time represents a significant drain on IT and operations time.
Moki’s Action Sequences address this directly. They allow administrators to define a series of device management actions, schedule them to execute at a specified time, and apply them to individual devices or entire device groups automatically. The task runs, the devices are affected, and the operations team does not need to be present or actively involved when the sequence executes.
Understanding how Action Sequences work, which tasks are best suited to automation, and how to build them effectively is the path from a reactive management posture to one where routine operations happen reliably without manual initiation.
What Action Sequences Are
An Action Sequence in Moki is a configured set of one or more device management actions that execute in order at a defined time, applied to a defined set of devices. The sequence is created in advance in the Moki dashboard, assigned to the target devices or groups, and scheduled to run without requiring anyone to be logged in or actively present at the execution moment.
Action Sequences can include a range of device management operations. Reboots are the most common use case, but sequences can also include configuration pushes, app updates, content delivery actions, and policy applications depending on the device type and platform. Multiple actions can be chained in sequence with defined timing between steps, allowing complex multi-step workflows to execute automatically.
For example, an Action Sequence for a nightly maintenance window might include: push any pending app updates to the device group, wait for the update installation to complete, then reboot all devices in the group to clear memory and apply the updates. The sequence runs at 2 AM, completes by 3 AM, and every device in the group starts the next operating day with current software and a clean memory state.
The Tasks That Benefit Most from Action Sequences
Not every device management task is a good candidate for automation through Action Sequences. The best candidates share two characteristics: they are routine and repeatable, and they can be safely executed without human review at the moment of execution.
Scheduled reboots are the highest-value Action Sequence use case for most kiosk and digital signage deployments. Applications that run continuously accumulate memory usage over the operating day. Without regular reboots, this accumulation leads to progressively degrading performance and eventually to application instability that manifests as crashes or frozen interfaces. A nightly reboot, timed to occur during the lowest-traffic window of the operating day, resets memory state and maintains consistent performance without affecting any customer interaction.
For self-ordering kiosks in restaurants, a nightly reboot after closing time and before the morning open is the natural maintenance window. For retail kiosks that operate during store hours, a reboot at 2 AM during the overnight closed period fits the same pattern. For 24-hour deployments like transit or hospitality kiosks, the lowest-traffic window of the operating cycle, typically the early morning hours, is the appropriate reboot window.
Off-hours configuration pushes are the second high-value use case. When a configuration profile change needs to be applied across a fleet, applying it during operating hours risks disrupting customer interactions during the profile update and reboot. An Action Sequence that pushes the configuration update and triggers a reboot at a scheduled off-hours time ensures the change takes effect cleanly without any customer-facing disruption.
Scheduled content delivery for content-driven deployments ensures that promotional content, menu updates, and campaign changes go live at the correct time without requiring anyone to manually initiate the push at the launch moment. A campaign that starts at 8 AM on a Tuesday is scheduled in advance and executes automatically. The operations team confirms the content is queued and live without needing to be at their desk at 8 AM to initiate it.
Verification sequences that check device status and confirm expected configuration after a maintenance window provide post-maintenance validation. After a nightly reboot sequence runs, a follow-up verification sequence confirms that devices are back online and applications are running correctly, generating an alert for any device that did not recover as expected.
Building an Effective Action Sequence
Creating an Action Sequence in Moki that performs reliably requires attention to several configuration details that determine whether the sequence runs cleanly or produces unexpected results.
Timing is the most critical configuration element. The sequence should be scheduled during the window when it will cause the least operational disruption: typically the period of lowest device usage in the operating cycle. For most customer-facing deployments, this is between midnight and 5 AM. Verify that the maintenance window does not overlap with any known operational requirements, such as overnight inventory processing that uses the same devices or early-morning content updates from a connected CMS that need the devices to be online.
Device group targeting determines which devices the sequence affects. A well-organized device group structure in Moki makes Action Sequence targeting precise and flexible. A nightly reboot sequence can target a device type group, a location group, or a combination, without affecting other device categories or locations. Testing the sequence on a subset of the target group before applying it to the full fleet is good practice for any sequence that includes a reboot or configuration change.
Sequencing order matters when multiple actions are included. Actions that require the device to be in a specific state before executing, such as a configuration push that should complete before a reboot is triggered, should be ordered accordingly with sufficient time between steps for the preceding action to complete.
For Android and BrightSign devices, Moki’s remote management capabilities support the full range of action types available in sequences. For iOS devices, the available actions reflect the platform’s MDM framework capabilities, which support scheduled reboots and configuration updates.
Monitoring Action Sequence Execution
Once Action Sequences are running on a scheduled basis, the operations team needs a way to confirm that sequences executed as expected and identify any devices that did not complete the sequence successfully.
Moki’s dashboard shows device status after a maintenance window, allowing the team to confirm that devices are online and in the expected post-sequence state. Any device that did not come back online after a scheduled reboot, or that did not receive a configuration push that was part of a sequence, should surface in the monitoring view and generate an alert through the standard alert configuration.
Building a brief daily review of device status into the morning operations routine, covering the devices that went through an overnight maintenance sequence, is a lightweight quality check that catches sequence failures before they affect the operating day.
Starting with One Sequence
For organizations that are not currently using Action Sequences, the recommendation is to start with a single, low-risk sequence: a scheduled nightly reboot for one device group. The reboot is the most universally beneficial automation, it carries minimal risk, and it demonstrates the operational value of automation in a concrete and measurable way before more complex sequences are built.
Once the nightly reboot is running reliably and the team is comfortable with how Action Sequences work in Moki, additional sequences for configuration pushes, content delivery, and verification can be added progressively until routine device management runs largely on autopilot.
Schedule a Moki demo to see Action Sequences configured and demonstrated for your specific device types, or start a free trial to begin building your first automated maintenance sequence. Moki’s support team can advise on the right sequence structure for your deployment type and operating hours.