wendy data campaign disarm
Switch a campaign off without removing it
Syntax
wendy data campaign disarm <campaign> [flags]Examples
wendy data campaign disarm --helpArguments
Argument notation from the CLI: <campaign>. Angle brackets mark required values; square brackets mark optional values. See Details for command-specific validation.
Flags
Flags below include inherited options. Types and defaults come from the CLI source. An empty default means no value is configured.
| Flag | Type | Default | Description |
|---|---|---|---|
--device | string | (empty) | Target device host (hostname, IP, or host:port); 'wendy run' accepts a comma-separated list to deploy one build to several devices (needs a remote build host and --detach). Defaults to $WENDY_DEVICE, then the saved default device |
--json | bool | false | Output in JSON format |
Output
Output depends on the operation and selected target. Use the command help for additional guidance..
JSON output
The global --json option requests machine-readable output. The CLI also selects JSON mode when no interactive terminal is attached. Support and payloads are command-specific; this flag does not guarantee a single JSON document for commands that stream logs or invoke build tools. Consult Details before parsing command output.
Exit codes
The CLI entry point returns 0 on success and for its user-cancelled or default-cleared results. Other returned errors exit with 1 and print a diagnostic to stderr. Some operations may terminate through subprocess or signal handling; do not infer application health from the CLI exit code alone.
Common errors
Check argument values and flag combinations against the synopsis above. For discovery, build, port, and readiness failures, see deployment troubleshooting. Command-specific constraints are in Details.
See also
Details
Disarm a deployed campaign: its triggers stop firing, its inference stops and its camera pre-roll is released, so the camera is no longer held for it. The plan, its revision and every recorded episode are kept, and the campaign stays disarmed across agent restarts, reboots and redeploys until it is armed again. A recording in progress is not cut short: it finishes its after_trigger window and is sealed normally.
Use the command help for additional guidance.