Actions56
- Acquisition Actions
- Asset Actions
- Baseline Actions
- Case Actions
- InterACT Actions
- Organization Actions
- Repository Actions
- Task Actions
- Triage Rule Actions
- User Actions
InterACT → Execute Async Command
AI-generatedOverview
The 'InterACT' resource's 'Execute Async Command' operation initiates an asynchronous command within an InterACT session, allowing for non-blocking execution of commands on a device. This is particularly useful for running long-duration tasks without waiting for their completion, thereby optimizing workflow efficiency.
Use Case Examples
- Initiating a system scan on a device without waiting for it to finish before proceeding with other tasks.
- Running a script that performs data analysis on a device while continuing to monitor other devices in parallel.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier for the InterACT session where the command will be executed. This is required to target the correct session. |
| Command | The specific command to be executed asynchronously within the InterACT session. This is required to define the action to be performed. |
| Response Type | The format in which the command's response will be returned. Options include 'JSON' for structured data and 'Text' for plain text responses. |
Output
JSON
status- Indicates the current status of the asynchronous command execution, such as 'pending', 'in_progress', or 'completed'.commandId- A unique identifier for the asynchronous command, useful for tracking or referencing the command in future operations.
Troubleshooting
- Ensure that the 'Session ID' corresponds to an active InterACT session to avoid errors related to invalid sessions.
- Verify that the 'Command' syntax is correct and supported by the device to prevent execution failures.
- If the 'Response Type' is set to 'JSON', ensure that the device's response is in a valid JSON format to facilitate proper parsing.