Skip "as logged in user" procedure if no user is logged in
J
James Holt
For any scheduled procedure set to "Run as Logged in User", there should be a "Skip if no user is logged in" checkbox to prevent unnecessary failures. A third-party application update procedure, for example, may fail for user space applications if no user is logged in. For some endpoints, this is a failure. For others, it is more of a situation where the procedure shouldn't have run.