reassigning ownership for large amount of knowledge objects


I see that when i reassigning ownership the schedule wont kick in (next_scheduled_time just reads none), for example until i open the search and manually hit save it seems like none of them will run on the original set time.

anyone ever run into this before? is there a rest call i can do to change the ownership based off the old owner?

0 Karma



Here you go for bulk modification of ownership of KO . Script given in Github repo works with python2 only, I am in process to convert that script for python3 and will be going to do some enhancement.

0 Karma

Ultra Champion

Sometimes I have noticed the UI does not always immediately calculate the next run date, but it does schedule correctly.

If you come back later, the UI updates and then the time is calculated correctly.
Also restarting Splunk seems to force it to refresh immediately

If my comment helps, please give it a thumbs up!
0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In the last month, the Splunk Threat Research Team (STRT) has had 2 releases of new security content via the ...

Announcing the 1st Round Champion’s Tribute Winners of the Great Resilience Quest

We are happy to announce the 20 lucky questers who are selected to be the first round of Champion's Tribute ...

We’ve Got Education Validation!

Are you feeling it? All the career-boosting benefits of up-skilling with Splunk? It’s not just a feeling, it's ...