cURL
curl --request GET "${HARNESS_URL}/harness/cronjobs/status" \
--header "Authorization: Bearer ${HARNESS_TOKEN}"import json
import os
from urllib.request import Request, urlopen
base_url = os.environ["HARNESS_URL"]
headers = {"Authorization": "Bearer " + os.environ["HARNESS_TOKEN"]}
request = Request(base_url + f"/harness/cronjobs/status", headers=headers, method="GET")
with urlopen(request) as response:
print(json.load(response))const baseUrl = process.env.HARNESS_URL;
const headers = { Authorization: `Bearer ${process.env.HARNESS_TOKEN}` };
const response = await fetch(`${baseUrl}/harness/cronjobs/status`, {
method: "GET",
headers,
});
if (!response.ok) throw new Error(await response.text());
console.log(await response.json());{
"replica_id": "replica-1",
"running": 0,
"concurrency": 8,
"last_scan_at": null,
"last_error": null,
"active": false
}Scheduled jobs
Get scheduler status
Inspect scheduling, running execution count, and the most recent scan on the replica serving this request
GET
/
harness
/
cronjobs
/
status
cURL
curl --request GET "${HARNESS_URL}/harness/cronjobs/status" \
--header "Authorization: Bearer ${HARNESS_TOKEN}"import json
import os
from urllib.request import Request, urlopen
base_url = os.environ["HARNESS_URL"]
headers = {"Authorization": "Bearer " + os.environ["HARNESS_TOKEN"]}
request = Request(base_url + f"/harness/cronjobs/status", headers=headers, method="GET")
with urlopen(request) as response:
print(json.load(response))const baseUrl = process.env.HARNESS_URL;
const headers = { Authorization: `Bearer ${process.env.HARNESS_TOKEN}` };
const response = await fetch(`${baseUrl}/harness/cronjobs/status`, {
method: "GET",
headers,
});
if (!response.ok) throw new Error(await response.text());
console.log(await response.json());{
"replica_id": "replica-1",
"running": 0,
"concurrency": 8,
"last_scan_at": null,
"last_error": null,
"active": false
}Requires a Harness Runtime deployed with AgentKit CLI 0.54.0 and scheduled tasks enabled
This endpoint describes only the replica serving the request. Different requests can report different replicas in a deployment with multiple replicas.
last_error is the most recently recorded scheduling error and is not guaranteed to clear immediately after a successful scanAuthorizations
Runtime access credential for a service-authenticated Harness, such as a Runtime API key; shared OAuth deployments do not support background scheduled tasks
Response
Success
Identifier of the replica serving this request
Number of executions currently running on this replica
Concurrency limit for this replica
Most recent completed scan on this replica in UTC; null before the first scan
Most recently recorded scheduling error identifier on this replica; null if none has been recorded
Whether this replica’s background scheduling is active; this is not a cluster-wide health result
Last modified on September 19, 2026