Open Jobs

A job must be opened in order for it to be ready to receive and analyze data. A job can be opened and closed multiple times throughout its lifecycle.


POST _xpack/ml/anomaly_detectors/{job_id}/_open


A job must be open in order to it to accept and analyze data.

When you open a new job, it starts with an empty model.

When you open an existing job, the most recent model state is automatically loaded. The job is ready to resume its analysis from where it left off, once new data is received.

Path Parameters

job_id (required)
(string) Identifier for the job

Request Body

(time) Controls the time to wait until a job has opened. The default value is 30 minutes.
[experimental] This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features. (boolean) If true (default), any gap in data since it was last closed is treated as a maintenance window. That is to say, it is not an anomaly


You must have manage_ml, or manage cluster privileges to use this API. For more information, see Cluster Privileges.


The following example opens the event_rate job and sets an optional property:

POST _xpack/ml/anomaly_detectors/event_rate/_open
  "timeout": "35m"

When the job opens, you receive the following results:

  "opened": true