Applicability
Splunk Enterprise
Description
A user wanted to upload report result into a dashboard and was going to use the loadjob feature with an already configured scheduled report for that.
Investigation
The
loadjob command can fail for a number of reasons, here some suggestions to try:
1. Try changing the owner of the scheduled job to nobody (instead of admin, and then change your loadjob command accordingly) (edit
local.meta within the app context of your saved search to do this)
2. The scheduled search could be getting skipped (check by going to Settings -> System Activity -> Scheduler reports)
3. The dispatch directory could be full for the admin user, check dispatch directory size and limits
4. The scheduled search name could be misspelled in the loadjob command
5. The app context that the saved search lives in could be incorrect in the loadjob command
Resolution
It turns out that the report was owned by nobody. It means that the user that created the object is no longer a user in the authenticating system. If you create a local user, then login as that user, then create any knowledge object, then delete that user, then all of his Knowledge Objects will switch to be owned by nobody.
Splunk Answers Why am I getting loadjob error "Cannot find artifacts for savedsearch_ident..." trying to get latest saved search results in Splunk 6.3? https://answers.splunk.com/answers/318096/why-am-i-getting-loadjob-error-cannot-find-artifac.html
What does 'nobody' (under owner column) signify in Splunk search and reporting?
https://answers.splunk.com/answers/425941/what-does-nobody-under-owner-column-signify-in-spl.html
Revision History
| Revision |
Publish Date |
Comments |
1.0 |
28-Sep-2026
|
Initial Release |