Stop data frame analytics jobs APIedit

Stops one or more data frame analytics jobs.


POST _ml/data_frame/analytics/<data_frame_analytics_id>/_stop

POST _ml/data_frame/analytics/<data_frame_analytics_id>,<data_frame_analytics_id>/_stop

POST _ml/data_frame/analytics/_all/_stop


Requires the manage_ml cluster privilege. This privilege is included in the machine_learning_admin built-in role.


A data frame analytics job can be started and stopped multiple times throughout its lifecycle.

You can stop multiple data frame analytics jobs in a single API request by using a comma-separated list of data frame analytics jobs or a wildcard expression. You can stop all data frame analytics job by using _all or by specifying * as the <data_frame_analytics_id>.

Path parametersedit

(Required, string) Identifier for the data frame analytics job. This identifier can contain lowercase alphanumeric characters (a-z and 0-9), hyphens, and underscores. It must start and end with alphanumeric characters.

Query parametersedit


(Optional, Boolean) Specifies what to do when the request:

  • Contains wildcard expressions and there are no data frame analytics jobs that match.
  • Contains the _all string or no identifiers and there are no matches.
  • Contains wildcard expressions and there are only partial matches.

The default value is true, which returns an empty data_frame_analytics array when there are no matches and the subset of results when there are partial matches. If this parameter is false, the request returns a 404 status code when there are no matches or only partial matches.

(Optional, Boolean) If true, the data frame analytics job is stopped forcefully.
(Optional, time units) Controls the amount of time to wait until the data frame analytics job stops. Defaults to 20 seconds.


The following example stops the loganalytics data frame analytics job:

POST _ml/data_frame/analytics/loganalytics/_stop

When the data frame analytics job stops, you receive the following results:

  "stopped" : true