๐ŸŽฏAPI Stability
Long-TermThis API is stable and will remain supported across versions with minimal breaking changes.

Summary

The enableScheduledSearchV2() mutation resumes execution of a scheduled search that was previously disabled. The search definition, query string, schedule expression, and associated actions are preserved across the disable/enable cycle. When re-enabled, the scheduled search runs on its configured schedule and triggers any associated actions. To pause execution without deleting the scheduled search, use disableScheduledSearchV2().

Syntax

graphql
enableScheduledSearchV2(
      input: EnableScheduledSearch!
   ): ScheduledSearch

The input argument takes an EnableScheduledSearch! object with two required fields: viewName, the name of the view or repository containing the scheduled search, and id, the unique identifier of the scheduled search to enable. See the Input Parameters section for details.

The mutation returns a nullable ScheduledSearch object. A null return indicates the scheduled search was not found. On success, the enabled field in the returned object is true, confirming that execution has resumed. See the Returned Values section for available fields.

Example

Raw
graphql
mutation {
  enableScheduledSearchV2( input:
    { viewName: "humio"
      id: "abc123" } ) 
  { id, enabled }
}
Mac OS or Linux (curl)
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
    -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" \
    -d @- << EOF
{"query" : "mutation {
  enableScheduledSearchV2( input:
    { viewName: \"humio\"
      id: \"abc123\" } ) 
  { id, enabled }
}"
}
EOF
Mac OS or Linux (curl) One-line
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
    -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" \
    -d @- << EOF
{"query" : "mutation {
  enableScheduledSearchV2( input:
    { viewName: \"humio\"
      id: \"abc123\" } ) 
  { id, enabled }
}"
}
EOF
Windows Cmd and curl
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql ^
    -H "Authorization: Bearer $TOKEN" ^
    -H "Content-Type: application/json" ^
    -d @'{"query" : "mutation { ^
  enableScheduledSearchV2( input: ^
    { viewName: \"humio\" ^
      id: \"abc123\" } )  ^
  { id, enabled } ^
}" ^
} '
Windows Powershell and curl
powershell
curl.exe -X POST 
    -H "Authorization: Bearer $TOKEN"
    -H "Content-Type: application/json"
    -d '{"query" : "mutation {
  enableScheduledSearchV2( input:
    { viewName: \"humio\"
      id: \"abc123\" } ) 
  { id, enabled }
}"
}'
    "$YOUR_LOGSCALE_URL/graphql"
Perl
perl
#!/usr/bin/perl

use HTTP::Request;
use LWP;

my $TOKEN = "TOKEN";

my $uri = '$YOUR_LOGSCALE_URL/graphql';

my $query = "mutation {
  enableScheduledSearchV2( input:
    { viewName: \"humio\"
      id: \"abc123\" } ) 
  { id, enabled }
}";
$query =~ s/\n/ /g;
my $json = sprintf('{"query" : "%s"}',$query);
my $req = HTTP::Request->new("POST", $uri );

$req->header("Authorization" => "Bearer $TOKEN");
$req->header("Content-Type" => "application/json");

$req->content( $json );

my $lwp = LWP::UserAgent->new;

my $result = $lwp->request( $req );

print $result->{"_content"},"\n";
Python
python
#! /usr/local/bin/python3

import requests

url = '$YOUR_LOGSCALE_URL/graphql'
mydata = r'''{"query" : "mutation {
  enableScheduledSearchV2( input:
    { viewName: \"humio\"
      id: \"abc123\" } ) 
  { id, enabled }
}"
}'''

resp = requests.post(url,
                     data = mydata,
                     headers = {
   "Authorization" : "Bearer $TOKEN",
   "Content-Type" : "application/json"
}
)

print(resp.text)
Node.js
javascript
const https = require('https');

const data = JSON.stringify(
    {"query" : "mutation {
  enableScheduledSearchV2( input:
    { viewName: \"humio\"
      id: \"abc123\" } ) 
  { id, enabled }
}"
}
);


const options = {
  hostname: '$YOUR_LOGSCALE_URL',
  path: 'graphql',
  port: 443,
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Content-Length': data.length,
    Authorization: 'BEARER ' + process.env.TOKEN,
    'User-Agent': 'Node',
  },
};

const req = https.request(options, (res) => {
  let data = '';
  console.log(`statusCode: ${res.statusCode}`);

  res.on('data', (d) => {
    data += d;
  });
  res.on('end', () => {
    console.log(JSON.parse(data).data);
  });
});

req.on('error', (error) => {
  console.error(error);
});

req.write(data);
req.end();
Example Responses
Success (HTTP Response Code 200 OK)
json
{
  "data": {
    "enableScheduledSearchV2": {
      "id": "abc123",
      "enabled": true
    }
  }
}

Input Parameters

Provide the id of the scheduled search to enable and the viewName of the associated view or repository. To retrieve a scheduled search identifier, use the Show Scheduled Searches Query in the Related section.

Returned Values

The mutation returns a nullable ScheduledSearch object. A null return indicates the scheduled search was not found or the caller lacks access to the specified view. On success, the enabled field is true, confirming that execution has resumed. The returned object also includes the query string, schedule expression, any configured action references, and the results of the last execution including errors and warnings. The following table lists all available fields.