Asset Backup Scheduler maintains a persistent Job History log that records every completed backup run — whether executed on schedule, manually triggered, or canceled by the user. The Job History is stored in AssetBackupSchedulerHistory.json in the application data folder and is automatically loaded on application startup, preserving the full history across restarts.
Accessing Job History
Navigate to the Job History tab in the main window to view the complete history of backup runs. Each entry in the history list represents a single backup run and can be expanded to view the detailed activity message log for that run.
Job History Entry Fields
Field
Description
Job Name
The name of the backup run as defined in the Scheduler appointment, or Manual Backup for runs triggered using the Start Backup Task button.
Job Description
A summary description of the backup run, including which job types were executed.
Status
The overall outcome of the backup run. See Status Values below.
Start Time
The date and time at which the backup run began.
End Time
The date and time at which the backup run completed, was canceled, or failed.
Duration
The total elapsed time of the backup run from start to end.
Snapshot Generated Time
The date and time at which Control Architect successfully generated a new Configuration Collection snapshot following the backup run. Only visible when snapshot auto-generation is enabled and a snapshot was successfully triggered.
Message Count
The total number of activity messages recorded during the backup run.
Activity Messages
A timestamped, chronological list of all activity, status, information, and error messages generated during the backup run. Each message has an associated message type (Information, Warning, Error) used for visual differentiation in the display.
Status Values
Status
Description
Completed
All enabled backup job types completed successfully. A green check indicator is displayed. If snapshot auto-generation is enabled, the snapshot was successfully triggered.
Warning
The backup run completed but one or more job types reported non-critical issues (e.g., a source file was not found, or a point type returned no records). An amber warning indicator is displayed. Review the activity messages for details.
Failed
One or more backup job types encountered a critical error and could not complete. A red error indicator is displayed. Review the activity messages log to identify the specific failure cause. See Troubleshooting for guidance.
Canceled
The backup run was stopped by the user using the Cancel Backup Task button. A grey cancel indicator is displayed. Partially collected assets may be present in the output folder.
Activity Message Types
Within each backup run history entry, activity messages are categorized by type and are visually differentiated in the message display:
Message Type
Description
Information
Normal operational status messages indicating progress, successful steps, and informational output from job processes.
Warning
Non-critical issues encountered during the backup run that did not prevent job completion but should be reviewed (e.g., missing optional files, empty point type result sets).
Error
Critical issues that caused a job step or the entire run to fail. Error messages include descriptive failure reasons to assist in diagnosing the root cause.
Snapshot Generation Timestamp
When Enable Snapshot Auto Generation is active in Settings, Asset Backup Scheduler notifies Control Architect at the conclusion of each successful backup run. If Control Architect successfully generates a new Configuration Collection snapshot in response, the Snapshot Generated Time field in the Job History entry is populated with the timestamp of the snapshot generation event.
If snapshot generation was not triggered (e.g., the auto-generation option is disabled, or the backup run failed), the Snapshot Generated Time field is not displayed for that history entry.
History Persistence
The Job History is automatically saved to %AppData%\Automation Software Technology, Inc\AssetBackupScheduler\AssetBackupSchedulerHistory.json at the conclusion of each backup run. The history file is loaded on application startup. History entries accumulate over time and are not automatically pruned — the history file will grow with each completed backup run.
Note: If the history file becomes very large over extended periods of operation, it can be safely deleted when the application is not running. Asset Backup Scheduler will create a new empty history file on next startup.
Tip: The color-coded status indicators in the Job History list provide an immediate at-a-glance view of backup run health over time. A pattern of Warning or Failed entries signals that a recurring connectivity or configuration issue should be investigated. See Troubleshooting for guidance.
