---
title: "wendy job submit"
description: "Start a named durable job; an identical retry returns the original receipt"
---

## Syntax

```sh
wendy job submit <spec.json> [flags]
```

## Examples

```sh
wendy job submit --help
```

## Arguments

Argument notation from the CLI: `<spec.json>`. 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 |
| --- | --- | --- | --- |
| `--artifact` | stringArray | `[]` | Selected relative report to retrieve after terminal evidence; repeat, requires --wait and --output |
| `--artifact-digest` | stringArray | `[]` | Collected file whose verified SHA-256 should appear inline; repeat, at most 16 files/4096 bytes |
| `--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` / `-o` | string | (empty) | Absolute local artifact directory; collection errors retain the confirmed job receipt |
| `--report-field` | stringArray | `[]` | Verified scalar field as relative.json#/pointer; repeat, requires --artifact, --wait and --output |
| `--wait` | int | `0` | Wait up to 3600 seconds for terminal evidence through bounded host RPCs; expiry never cancels the job |
| `--workflow` | bool | `false` | Read a saved wendy.workflow.v1 execution/evidence contract instead of a plain job specification |

## 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](../../../../errors/). Command-specific constraints are in Details.

## See also

- [wendy job](../../../../reference/cli/job/)
- [CLI conventions and configuration](../../../../reference/)

## Details



Use the command help for additional guidance.