Depending on the timing when the search/jobs endpoint is queried, the endpoint may list some jobs that are still in transient state. These jobs are in this state for a very brief period. Ultimately, these jobs will have a legitimate dispatchState.
Example:
The following search job was picked by running (looped non-stop for testing purpose).
curl -k -u admin:password https://localhost:8089/services/search/jobs?output_mode=json | jq
This was a "transient" job, which did not have any dispatchState. Also worth noting is the published date, which was an epoch date.
{
"name": "",
"id": "https://localhost:8089/services/search/jobs/1645699431.5841220_221A5361-ECCE-4536-97C7-31B6C66E27D8",
"updated": "1969-12-31T19:00:00.000-05:00",
"links": {
.
.
},
"published": "1969-12-31T19:00:00.000-05:00",
"author": "splunk-system-user",
"content": {
"cursorTime": "1969-12-31T19:00:00.000-05:00",
"defaultSaveTTL": "604800",
"defaultTTL": "600",
"delegate": "",
"doneProgress": 0,
"earliestTime": "1969-12-31T19:00:00.000-05:00",
"isFailed": false,
"isPaused": false,
"isSavedSearch": false,
"label": "",
"sid": "1645699431.5841220_221A5361-ECCE-4536-97C7-31B6C66E27D8",
"statusBuckets": 0,
"ttl": 0,
"messages": [],
"searchProviders": []
Soon after, however, it turned up with the correct info (picked by the next curl run):
"id": "https://localhost:8089/services/search/jobs/1645699431.5841220_221A5361-ECCE-4536-97C7-31B6C66E27D8",
"updated": "2022-02-24T05:43:52.057-05:00",
"links": {
.
.
},
"published": "2022-02-24T05:43:51.000-05:00",
"author": "splunk-system-user",
"content": {
"canSummarize": false,
"cursorTime": "1969-12-31T19:00:00.000-05:00",
"defaultSaveTTL": "604800",
"defaultTTL": "600",
"delegate": "",
"diskUsage": 139264,
"dispatchState": "DONE",
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |