---
title: blossom job:update
url: "/docs/reference/cli/job/update/"
canonical_url: https://docs.blossom88.com/docs/reference/cli/job/update/
markdown_url: https://docs.blossom88.com/docs/reference/cli/job/update.md
summary: Update a Job definition without changing previous Runs
categories:
- cli
- reference
---

# blossom job:update

Update a Job definition without changing previous Runs

## Usage

    blossom job:update --id ID [--data DATA]

## Flags

| Flag | Description |
| --- | --- |
| `--id (required)` | Job id |
| `--data, -d` | YAML or JSON definition, file path, or HTTP(S) URL |

## Examples

    blossom job:update --id job-100 --data job.yml

Update only the settings you want to change. Existing Runs retain their
original snapshots. Schedule settings stay in the data file, not CLI flags.

Omitting sizing preserves the saved policy. Set `size: inherit` under `job`
to match your Environment's largest Service requirements for future Runs.
An explicit size stays fixed until changed. `job:show` shows the resolved size.

schedule.yml:

```yaml
job:
  schedule:
    cron: "0 2 * * *"
    time_zone: Etc/UTC
    enabled: true
    overlap_policy: skip
```

    blossom job:update --id job-100 --data schedule.yml
    blossom job:show --id job-100

The example runs daily at 02:00 UTC within approved Capacity. Skip records a
non-executed occurrence when an earlier Run is active or awaiting cleanup, or
admission exceeds your Account allowance. Accepted Runs may wait for Capacity.
Set `schedule.enabled: false` to disable future Runs;
accepted Runs are not canceled. `job:write` authorizes schedule changes.