Symantec Privileged Access Management

 View Only

 How to Check the Execution Results of a Defined Job

MARUBUN SUPPORT's profile image
MARUBUN SUPPORT posted Mar 19, 2026 05:23 AM

Hi Team,


I received a question from a customer and would appreciate your advice.

---
I have registered a scheduled job to update the password for a target account.
Please tell me how to check the execution results (successful completion or failure) of the defined job.
If there is a log where the execution results are output, please let me know where it is located.
---

Regards,

Ralf Prigl's profile image
Broadcom Employee Ralf Prigl

Hello, PAM has two reports that you can run to get details on scheduled job performance, both accessible from the Credentials > Reports > Run page. The Scheduled Jobs report will provide overall scheduled job results. Note that the job will be regarded a failure as soon as one of the password updates inside the scheduled job fails. To get details on which update(s) failed, you use the Account Passwords Update Attempts report. It will list all password update attempts and include information on whether the update was initiated by a PAM user or by a scheduled job.

All information that is used to generate the reports also is sent to the configured syslog server, and you could create your own reports on your SIEM solution, see e.g. KB Email Notifications when a PAM Job runs successfully.

Joseph Fry's profile image
Broadcom Employee Joseph Fry

There are a couple of easy ways to confirm the password was rotated at the scheduled time:

  1. Look at the target account credential history in the PAM UI:
  2. Use the "scheduled jobs" or "account password update attempts": report under Credentials > Reports > Run

Of course you can also use the CLI (or new APIs on upcoming 4.3.1 release) to gather this information.

If the scheduled job fails an event is logged to the tomcat diagnostic log by default.  I didn't verify but it should log successful attempts as well if you increase the logging level to info.  I also didn't check to see if anything is logged to syslog.