Cloud discovery schedules get the creator as "Runs as", and it is not possible to change.

[Johannes]

When creating a "Cloud discovery", the schedules get the creator as "Runs as", and it seems like it is not possible to change this. Is this correct? Why on earth is it not possible to change it to a system user, so that the job does not fail if the person is inactivated?

[Fabian Kunzke]

Just from my experience: I never had one of these schedules failed based on their "Run as" value. However, this should be an easy thing to check. Could you verify this on a non-production instance? I am pretty sure the schedules will run even without the user being active.

Other than that you could post this default value issue as an improvement request towards service now.

Regards

Fabian

[Johannes · Accepted solution]

Turned out the reason for the jobs not being editable was that they was created in another application scope than Global. Changing to that scope allowed me to change the "Run as". Why they were created in another scope in the first place is still unknown, but mystery solved. Thanks for your responses, Fabian!