Command history and status

Every remote command sent to a supported device is logged with a status. This article explains what each status means and what to do for each.

Pending

CastHub created the command and is waiting for the device to pick it up. Devices check in on a short interval, so Pending should resolve within seconds for an online device. If a command sits at Pending for more than a minute or two, the device is probably offline.

Executing

The device has received the command and started processing it. Reboot, cache clear, and display power commands typically resolve within a few seconds. Screenshot commands take a little longer because the device has to capture and upload an image.

Completed

The command finished successfully. For screenshots, the captured image is available in command history; click into the entry to view it.

Failed

The command did not complete. Check the device’s online status; check that the connected display supports HDMI CEC if a display power command failed; check the device for storage or hardware issues if a reboot or cache clear failed. Send the command again after addressing the underlying issue.

Rate limited

The device or the management service temporarily rejected the command because too many commands were issued in a short window. Wait a minute and resend. If you see Rate limited frequently, batch your commands instead of sending many at once.

What to do when nothing seems to be happening

Confirm the device is online from the Devices page. Confirm the command type is supported on that platform (remote commands are currently focused on Amazon Signage Stick). Try Reboot first; it is the most universally supported command and resolves a wide range of issues on its own.