Skip to content
Innomesh Docs
Portal Since v3.6.0

Scheduled Actions and History

The Actions page is the single view of every asset action in the platform, whether it came from an automation policy or was triggered directly by a user. Use it to see what is about to happen, confirm what already did, and cancel work you no longer want.

Navigate to Assets > Actions. The page has two tabs: Schedule for upcoming actions, and History for actions that have already run.

Schedule

The Schedule tab is a forecast of pending actions.

Schedule tab listing six pending actions with clock status icons, scheduled time, room, asset, action, parameters, type, and origin columns
Pending actions from three policies. The first four run on one panel ten seconds apart, showing how actions on the same asset are staggered.
ColumnDescription
StatusThe action’s current state
Scheduled TimeWhen the action will run, converted to your local timezone
Room NameThe room the asset sits in
Asset NameThe target device, linked to its Asset Information page
Category, Brand, ModelThe device’s identity, matching its asset profile
ActionThe operation to be performed, such as Set Input or Reboot
Parameter(s)The values the action will apply, such as Input: HDMI1
TypeThe action’s cadence and what triggered it
OriginThe policy that created the action, linked to the policy itself, or the user who triggered it

Key behaviours:

  • Origin is a link. Administrators with the right permissions can click through to open and edit the policy that created the action.
  • Only the next occurrence is shown for recurring policies. Once today’s actions complete, the list refreshes to show tomorrow’s.
  • The page updates itself as actions progress, so a run can be watched without reloading.
  • Filters and sorting are available per column, and the Columns button shows or hides columns.
  • User-triggered actions appear here too, which makes this the one place to check before touching a device manually.

Removing Queued Actions

Select one or more rows using their checkboxes and click Delete.

📝 Note
Deleting a scheduled action does not disable the policy that created it. The policy will recreate the action on its next trigger, whether that is tomorrow’s schedule, the next matching alert, or the next hourly compliance evaluation. To stop actions for good, disable or delete the policy.

Cadence and Trigger Labels

The Type column names both how often an action recurs and what scheduled it.

TypeMeaning
Recurring (Custom)A time-based policy running at a custom time on selected days
Recurring (Maintenance Window)A time-based policy running inside a maintenance window
One-Time (ASAP)An alert-based or property-based policy set to ASAP, or an action a user triggered directly
One-Time (Maintenance Window)An alert-based or property-based policy deferring to a maintenance window
📌 Since
These labels were introduced in v3.6.1. Actions queued before the upgrade continue to show the older bare Recurring and One-Time values until they run and age out.

History

The History tab lists actions from the last 24 hours with their outcomes.

History tab listing ten actions, nine with green tick icons and one with a red cross
Outcomes for the previous 24 hours. All nine actions of one policy ran on the same panel, one of them failing, which is why the whole action list appears rather than just the setting that drifted.
StatusMeaning
CompletedThe action ran successfully
FailedThe action encountered an error during execution
Timed OutNo status update was received within the expected time
CancelledThe action was cancelled before running, for example because its alert resolved first

Hover a status icon for additional detail about that execution. This is the fastest way to distinguish a policy problem from a device problem: an action that reached Failed or Timed Out was dispatched correctly, so the fault usually lies with device credentials, network reachability, or the device itself.

For a longer view of a single device’s activity, open its Asset Information page. See Asset Information.