Troubleshooting Error Messages

When an action can't run, ChassisWatch records it in the History tab as Failed or Timed out, usually with a short message explaining why. The same message appears when you click Test Action or Test Actions in the automation editor. If an action fails, the actions after it in the same automation don't run.

Find the message you're seeing below. Most fixes happen in the automation editor: open Settings, go to Automations, and double-click the automation.

License and permissions

"An active license is required to execute actions."

ChassisWatch has no active license on this Mac. This happens if the license was deactivated, moved to another Mac, or couldn't be revalidated for more than 14 days while offline. Open Settings > License and activate your key again, or connect to the internet so it can revalidate.

"This action needs Accessibility access before it can run."

Press Keyboard Shortcut and the media key actions (Play/Pause, Next Track, Previous Track) need Accessibility access, and it's missing or was turned off. See how to grant Accessibility permission. You may also see this as "Accessibility access is required to post keyboard and media-key events."

"This action needs Notifications access before it can run."

Show Notification needs permission to post notifications. Open Settings > General, find Permissions, and click Request Access, or turn on notifications for ChassisWatch in System Settings > Notifications. Related messages: "Notification permission has not been requested." and "Notification permission is denied."

Missing files, apps, and devices

"The selected action resource is unavailable."

The action points to something ChassisWatch can't find right now. The automation also shows Needs Attention in the Automations list. Common causes:

• A file, folder, or app used by the action was moved, renamed, or deleted.
• An Apple Shortcut used by Run Apple Shortcut was renamed or deleted.
• A sound file used by Play Sound was moved or deleted.
• A script file, working directory, or custom interpreter used by Run Shell Script is gone.
• The hardware the action controls isn't there. For example, Set Built-in Display Brightness while the lid is closed, or Toggle Mute and Set System Output Volume when the current audio output has no volume control.

To fix it, open the automation, edit the action, and pick the file, app, Shortcut, or sound again. For hardware, try again once the device is connected or the lid is open.

"The selected file or application is unavailable."

Open Application or Open File or Folder can't find its target. Edit the action and choose the app, file, or folder again.

"The selected sound is unavailable." / "The selected sound cannot be played."

The sound file was moved or deleted, or it's in a format macOS can't play. Edit the action and pick a different sound.

"The selected speech voice is unavailable."

Speak Text is set to a voice that isn't installed on this Mac. Pick another voice, or download it in System Settings > Accessibility > Spoken Content.

"The selected removable volume is not mounted." / "The selected volume is not removable."

Eject Removable Volume couldn't find the drive, usually because it's already unplugged or ejected. If the drive is connected, edit the action and select it again.

"No active built-in display is available. Open the MacBook display and try again."

Set Built-in Display Brightness only works while the MacBook's own screen is on. It fails with the lid closed, for example when using an external display in clamshell mode.

"No default output device is available." / "The default output device does not expose a controllable volume." / "The default output device does not expose mute control."

The current sound output doesn't let macOS change its volume or mute it. Some HDMI, DisplayPort, and USB audio devices work this way. Switch to a different output in System Settings > Sound, or control the volume on the device itself.

Scripts and Shortcuts

"The selected script, interpreter, or environment value is unavailable."

Run Shell Script couldn't get everything it needs to start. The script file, working directory, or custom interpreter may have moved, or an environment variable stored in the Keychain couldn't be read. Edit the action and pick the missing file again, or re-enter the secret value.

"The script exited with status N."

The script ran but reported an error by exiting with a non-zero status. This comes from the script itself, not ChassisWatch. Run the same script in Terminal to see its output, then fix the script.

"Choose a Shortcut before saving this action."

The Run Apple Shortcut action has no Shortcut selected. Edit the action and choose one.

"Shortcuts is unavailable on this Mac."

ChassisWatch couldn't find the tool macOS uses to run Shortcuts. Make sure the Shortcuts app is installed and opens normally, then try again.

"The selected Shortcut is already running."

The same Shortcut was still running from an earlier trigger. Wait for it to finish, or add a cooldown to the automation so it can't fire again so quickly.

"The selected Shortcut could not complete." / "macOS could not start the selected Shortcut."

The Shortcut started but failed, or macOS refused to start it. Open the Shortcuts app and run it there to see which step fails.

"The selected Shortcut timed out." / "The selected Shortcut was cancelled."

The Shortcut took too long, or it was stopped before it finished. Check it in the Shortcuts app for steps that wait for input or take a long time.

Other messages

"This action is not available yet."

The action's settings aren't complete. For example, Speak Text with no text, or Open URL with an address that's missing https://. Edit the action and fill in the missing value.

"Screen locking is unavailable on this Mac." / "Notifications are unavailable on this Mac."

macOS didn't provide the feature ChassisWatch uses for Lock Screen or Show Notification. Restarting the Mac usually clears this. If it doesn't, check that you're on a supported macOS version.

"macOS could not…" messages

Messages that start with "macOS could not", "macOS rejected", "CoreAudio could not", or "DisplayServices could not" mean macOS refused the request at that moment. For example: "macOS could not deliver the notification.", "macOS could not eject the selected removable volume.", or "macOS rejected the sleep request". These are usually temporary. Try Test Action again. For eject, close any apps that are using files on the drive first.

"The private DisplayServices framework is unavailable on this macOS version."

Set Built-in Display Brightness relies on a macOS component that isn't available in your macOS version. The action can't run on this Mac until ChassisWatch is updated to support it.

Results without a message

Timed out

The action ran longer than its time limit and was stopped. For Run Shell Script, you can raise Timeout (seconds) in the action's settings if the script legitimately needs more time.

Cancelled

The action was stopped before it finished because you paused monitoring, disabled the automation, quit ChassisWatch, or the Mac went to sleep. Nothing needs fixing.

Failed, with no message

macOS reported an unexpected error without details, or the action's app or script couldn't be launched. Try Test Action again. If it keeps failing, email support@chassis.watch and mention which action and trigger you're using.