Last Updated: November 10, 2026
Overview
From the Incidents list you can run a command without building a playbook. There are two ways in:
-
Execute Command, the ⌘ button at the bottom right of the list, runs a command on its own with the parameters you enter.
-
Execute command, the ⌘ icon at the top of an incident's quick view panel, runs a command from that incident.
Both list utility commands and integration commands. Each command shows its description, its category and whether it is a utility command or which integration it belongs to.
WARNING
Run Command runs the command. An integration command acts on the system it connects to: for example, Add Access Rule creates a new access rule in CheckPoint Firewall, as its description says. Read the description and check every parameter before you select Run Command.
Running a Command from the Incidents List
-
On the Incidents list, select Execute Command (⌘) at the bottom right.
The Execute Command window
-
Find the command. Choose a category on the left, such as All, Array or Endpoint Security, each with the number of commands it holds, or type in Search commands.... Each card shows the command's name, description and category, and the integration it belongs to.
-
Select the command's card. The window shows the command at the top, marked Selected Command, and its Command Parameters: "Fill in the following command input parameters and start running it". Each parameter shows its type, such as Text Array.
-
Optionally, select Sample Data to see example values for the command, on its Input and Return Data tabs.
-
Enter the parameters, then select Run Command.
The command parameters
Most commands show their results under Execution Results, on the Return Data, Context Data, Key Fields and Raw Data tabs. Until a command runs, they read "No results yet". The back arrow beside Execute Command returns to the list of commands, and × closes the window.
READER NOTE
A command built as a Codeless Playbook starts a playbook and does not wait for it to finish, so it has no results to show here. A message confirms [command name] started and is running in the background, and the window shows the same message with the line It is not tied to an incident, so its status is not shown here. The tabs under Execution Results read No results yet and The command is running in the background. Because the run is not tied to an incident, D3 Morpheus does not show its result: it has no Command Centre entry, and it is not listed in Command Logs, which keeps test runs. To see a Codeless Playbook command's result, run it from the incident instead, from its quick view panel or its workspace.
Running a Command on an Incident
-
On the Incidents list, select anywhere on the incident's row except its number. The quick view panel opens on the right. See Previewing an Incident.
-
At the top of the panel, select Execute command (⌘). The Execute a Command window opens.
Execute command in the quick view panel
-
Choose the command. Type its name in Search or select a command, or select the more icon (⋮) beside it to browse in the Select Command window. There, filter by category (All by default), search with Search Commands, and select a command to see its description and a Sample Data Preview on the Input and Return Data tabs. Select Select to use it.
The Select Command window
-
The window shows the command's description and its Command Parameters. View Sample Data shows example values. Enter the parameters, then select Run Command.
The Execute a Command window
Following a Command's Run
What you see after you select Run Command depends on how the command is built. A command's implementation type shows on the command's page in Utility Commands.
-
Codeless Playbook: the command starts a playbook run on the incident and does not wait for it to finish. The window reports the run's progress, as described below.
-
Every other command runs at once and shows its result in Outputs, on the right of the window.
When a Codeless Playbook command starts, a message confirms [command name] started and is running in the background. A status panel then appears in the window, between the command's description and Command Parameters. It shows a status badge, the command's name and a message saying what the run is doing, and it updates on its own while the window stays open.
The status of a running command
|
Badge |
What it means |
|---|---|
|
Started |
The run has started and its first status has not come back yet. |
|
Waiting to run |
The run is queued. Running the command again does not make it start sooner. |
|
Running |
The run is in progress. You can close the window: the result goes to the incident's Command Centre when the run finishes. |
|
Waiting |
One of the run's tasks is waiting, for example on a person, a reply or another step. |
|
Error |
A task in the run hit an error. The run is still open. |
|
Done with errors |
The run ended, and at least one of its tasks hit an error. |
|
Done |
The run ended. |
|
Cancelled |
The run was cancelled outside this window, for example on the incident's Playbooks page. |
|
Not started |
The run did not start any task. |
When the run ends Done, the message reads [command name] finished. Its result is in the Command Centre. For a single run that ends Done or Done with errors, the result also appears in Outputs.
READER NOTE
The window checks the run's status for 10 minutes. After that, the badge keeps the last status it showed and the message adds Stopped checking after 10 minutes - the run is still open. The run itself carries on, and its result goes to the incident's Command Centre when it finishes.
The status panel belongs to the window that started the run. If you close the window and open it again, the panel is gone; follow the run in the incident's Command Centre instead.
Running a Command That Is Already Running
Running a Codeless Playbook command that is still running on the same incident asks first, so the incident does not end up with duplicate runs by accident.
Confirming a repeat run
The confirmation is titled [command name] is already running on this incident. It says who started the latest run and when, its current status, how many runs of the command are active when there is more than one, and that running it again queues another run of the same playbook.
-
Cancel runs nothing and keeps the parameters you entered. Cancel is selected by default.
-
Run again starts another run.
READER NOTE
The confirmation compares only the command and the incident, not the parameters: it asks even when you have entered different values. It is a warning, not a block; Run again always starts the new run.