The following information is useful when troubleshooting Robot-related issues.

When the Robot starts up, if set to verbose it logs the following information to its log file: 

• The startup test result for each active job
• The addition of each job to the schedule, along with the date the job was created plus its currently assigned cron value

 Then on each run of each job, it will log the activity:

• In its log file
• In the database table RobotJobHistory

However, there are some anomalies.

• Not all jobs add an entry to the RobotJobHistory table when they run.  These are:

SendRejectionEmails.ActionUpdate
UpdateRetain
UpdateSegmentationLists
UpdateHierarchyProperties
GetFromRetain
EmailErrorLogs

• While all the jobs run according to their cron value per the server's clock time, most jobs report their "starting:" time in UTC.  The exceptions are the following ones, which report their starting time as their cron value:

UpdateDueDateVariances
UpdateProcessNames
CreateActionUpdates
SendInitialEmails.ActionUpdate
SendReminderEmails.ActionUpdate
SendRejectionEmails.ActionUpdate
UpdateRetain
GetFromRetain
PurgeAuditTrail.TimeSheet
RefreshTimeSheets

Note that timestamps in the Robot's email log file will be UTC.