---
title: stack es rollup stop-job cli command
description: Stop rollup jobs. Behaviour flags: --dry-run — validate all inputs and exit without performing any action 
url: https://docs-v3-preview.elastic.dev/elastic/cli/pull/525/cli/stack/es/rollup/stop-job
---

# stack es rollup stop-job cli command
<cli-modifiers>
</cli-modifiers>

```bash
elastic stack es rollup stop-job --id <id> [options]
```

Stop rollup jobs.
**Behaviour flags:**
`--dry-run` — validate all inputs and exit without performing any action

## Options

<definitions>
  <definition term="--id string required">
    Identifier for the rollup job.
  </definition>
  <definition term="--timeout string">
    If `wait_for_completion` is `true`, the API blocks for (at maximum) the specified duration while waiting for the job to stop.
    If more than `timeout` time has passed, the API throws a timeout exception.
    NOTE: Even if a timeout occurs, the stop request is still processing and eventually moves the job to STOPPED.
    The timeout simply means the API call itself timed out while waiting for the status change.
  </definition>
  <definition term="--[no-]wait-for-completion">
    If set to `true`, causes the API to block until the indexer state completely stops.
    If set to `false`, the API returns immediately and the indexer is stopped asynchronously in the background.
  </definition>
  <definition term="--[no-]error-trace">
    When set to `true` Elasticsearch will include the full stack trace of errors
    when they occur.
  </definition>
  <definition term="--filter-path string">
    Comma-separated list of filters in dot notation which reduce the response
    returned by Elasticsearch.
    **Repeatable:** pass `--filter-path` multiple times to supply more than one value
  </definition>
  <definition term="--[no-]human">
    When set to `true` will return statistics in a format suitable for humans.
    For example `"exists_time": "1h"` for humans and
    `"exists_time_in_millis": 3600000` for computers. When disabled the human
    readable values will be omitted. This makes sense for responses being consumed
    only by machines.
  </definition>
  <definition term="--[no-]pretty">
    If set to `true` the returned JSON will be "pretty-formatted". Only use
    this option for debugging only.
  </definition>
  <definition term="--input-file string">
    path to a JSON file to use as command input
  </definition>
  <definition term="--[no-]dry-run">
    validate all inputs and exit without performing any action (preview changes without applying them)
  </definition>
</definitions>


## Global Options

<definitions>
  <definition term="--[no-]json">
    output as JSON
  </definition>
</definitions>