Autosys incorrectly starting jobs elevated
search cancel

Autosys incorrectly starting jobs elevated


Article ID: 247413


Updated On:


Workload Automation Agent CA Workload Automation AE CA Workload Automation AE - Scheduler (AutoSys)


Hi Team,

We have removed elevated, interactive modes, and tested an entry in the agent parm settings that is supposed to ensure the elevated attribute in a job definition is in use, in this case we expect the job to start as non-elevated as the check box is not ticked.

Here is setting tested:


But why a job would be starting as elevated, when it is set to run as non-elevated?

Please suggest why this is happening & steps to fix it.



Release : 11.4

Component : Workload Automation System Agent


Couple of solutions to get around this:

  1. Implement starting conditions to prevent jobs that do not require elevated permissions from processing in parallel with those that do. This will prevent elevated permissions from being inherited by the next job to process.
  2. Perhaps use a different batch user account for these DIF jobs, or
  3. Install a second agent on the server and point the DIF jobs to that agent.