Overview

The 'Interrupt Command' operation within the 'InterACT' resource of the AIR node in n8n is designed to halt an ongoing command execution in an active InterACT session. This functionality is particularly useful when a command is taking longer than expected or is no longer needed, allowing users to maintain control over device interactions by terminating specific commands without ending the entire session.

Use Case Examples

1. A user initiates a command to retrieve system logs from a device, but the process is taking too long. Using the 'Interrupt Command' operation, the user can stop this specific command, allowing them to issue a new command or close the session without waiting for the previous command to complete.
2. During a security assessment, a command to scan for vulnerabilities is running longer than anticipated. The 'Interrupt Command' operation enables the user to terminate this command, enabling them to run a different command or adjust their approach without waiting for the initial command to finish.

Properties

Output

JSON

• status - Indicates the success or failure of the interrupt command operation. A value of 'success' confirms that the command was successfully interrupted, while 'failure' indicates an issue occurred during the process.

Dependencies

• An active InterACT session with a valid session ID.
• The message ID of the command that is currently being executed and is intended to be interrupted.

Troubleshooting

• Ensure that the session ID and message ID are correct and correspond to an active command in the InterACT session.
• Verify that the InterACT session is active and not already closed, as interruptions cannot be performed on closed sessions.
• Check for network connectivity issues that might prevent the interruption command from reaching the target device.

Links

• Execute Command Node Documentation - Provides detailed information on the Execute Command node in n8n, which can be relevant for understanding command execution within workflows.