Skip to main content
Actions

Shut down device

What the Shut down device action does, which settings it has, and when the step fails.

Shut down device powers off the device, optionally after a delay. The device must be online.

Configuration fields

FieldTypeRequiredDefaultDescription
Delay (seconds)numberNo0How long the device waits before it shuts down. Values below 10 seconds are raised to 10 seconds. Linux and macOS only schedule shutdowns in whole minutes, so there the delay is rounded up to the next full minute, at least one minute
Reason (optional)textNo—Passed to the operating system on Windows and Linux; macOS does not use it. Supports variables ${{ … }}. If you leave it empty, octoja uses Automation: followed by the automation's name

Platform support

PlatformSupported
WindowsYes
LinuxYes
macOSYes

Outputs

This action produces no outputs.

Result behaviour

The step succeeds as soon as the operating system has scheduled the shutdown. That does not yet tell you the device is actually off. If the operating system rejects the command, the step fails. On Windows, a restart or shutdown that is already scheduled also counts as success.

The workflow does not wait for the shutdown, so the next step starts immediately. A later step that needs the device may still reach it during the delay. After that it finds the device offline, and its If device is offline setting applies.

If the device is already offline when the step starts, the step does not run and is marked Device offline. If device is offline then decides whether the run ends or the step is skipped.

The device stays off until someone switches it on or wakes it. Logged-in users are signed out and unsaved work can be lost. Warn users with the delay and reason, or add a Send notification step before this one.

See also: Create an automation · Restart device · Wake device

Was this helpful?

Still need help? Ask the team