# Schedule the reboot boundary for an Axis capture mode change > Axis Capture mode changes do not take effect until after reboot. Plan the configuration and effective-state checks as separate parts of an authorized camera change. - Canonical URL: https://update.dsesecurity.com/updates/schedule-the-reboot-boundary-for-an-axis-capture-mode-change/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-10-29T00:10:14+00:00 - Modified: 2026-10-29T00:10:34+00:00 - Last reviewed by DSE: 2026-10-28 - Resource type: Guide - DSE priority: Advisory - Topics: IT, Video Surveillance - Reading time: 3 minutes ## What you need to know Axis Capture mode changes do not take effect until after reboot. Plan the configuration and effective-state checks as separate parts of an authorized camera change. ## Potentially affected Axis devices exposing the documented Capture mode interface; confirm support and the installed API/software scope before applying the proposed checks. ## DSE recommendation DSE recommends recording both the requested mode and the effective post-reboot mode in the change worksheet. ## Article Bottom line: Do not close a capture-mode change at the configuration response; schedule and verify the documented reboot boundary. ## Source fact: documented behavior The [Capture mode](https://developer.axis.com/vapix/network-video/capture-mode/) documentation says the query returns current and available capture modes for each channel. Its change example states that a new capture mode does not take effect until after a reboot. The response description guarantees the optional maxFPS field only when that mode’s enabled value is true. ## What the source does not establish Do not use an available-mode description as a promise of recorded frame rate through a complete surveillance system. Keep mode selection, device restart and recorder acceptance as separate checks. Confirm exact device and channel support before choosing a mode. Use a supported restart procedure and an approved interruption plan rather than inventing a command or assuming the change is immediate. ## Applicability questions - Which channel and returned mode identifier are actually being changed? - What current mode and enabled-state evidence should be preserved first? - When can the required reboot occur without an unplanned recording interruption? - Which device-state and recording checks will establish the intended result afterward? ## DSE recommendation: controlled next steps The following steps are DSE recommendations based on the cited source. DSE recommends recording both the requested mode and the effective post-reboot mode in the change worksheet. - Read the supported current-and-available mode information for the exact channel on a representative test device. Preserve the returned identifiers and enabled state. Have the camera and recording owners approve the proposed mode for the task. Avoid copying an identifier from another model or channel simply because a friendly description looks familiar. - Apply the documented configuration through the supported interface and record its response. Mark the effective-state check as pending until the approved reboot and recovery procedure has completed. Coordinate the interruption with the recording owner and preserve the accepted pre-change configuration. Do not allow a successful setting response to close the entire maintenance task. - After the planned reboot, query the channel again and compare its enabled mode with the approved target. Then verify the required recording workflow independently, using an authorized test scene and retrieved footage. If the device state or recording result is unacceptable, follow the approved restoration plan and retain both the unsuccessful and restored observations. ## Verification and evidence Keep device/software identity, channel, original and target mode identifiers, before-and-after query results, configuration response, reboot times and restoration evidence. Treat the returned optional frame-rate field according to its documented enabled-mode condition; do not fill an absent value with an assumed specification. For the proposed handoff exercise, show a completed configuration request alongside a still-pending reboot and ask the operator whether the change is finished. Require the effective-state and recording checks before acceptance. This article reports no reboot, measured frame rate or demonstrated compatibility between a capture mode and a recorder. ## Official references - [Capture mode](https://developer.axis.com/vapix/network-video/capture-mode/) — Axis Communications; official VAPIX documentation. Source review completed October 28, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings. ## Primary reference - Name: Axis Communications — Capture mode - Authority: Axis Communications - URL: https://developer.axis.com/vapix/network-video/capture-mode/ - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Schedule the reboot boundary for an Axis capture mode change,” DSE Security, https://update.dsesecurity.com/updates/schedule-the-reboot-boundary-for-an-axis-capture-mode-change/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.