Enabling Job History
Job history tracking is not active by default. Before the dashboard will record any runs, you must turn it on in the application settings.
Open Settings
From the main menu bar, click Settings to open the Settings dialog.
Go to the Miscellaneous tab
Select the Miscellaneous tab inside the Settings dialog.
Enable Job History Tracking
Check the Enable Job History Tracking option and click Save. Once enabled, every job run — scheduled or manual — is recorded in the Job History dashboard.
Overview
The Job History tab presents a live table of every export job that has been created — whether scheduled to repeat on a timed schedule or run once on demand. Each row represents one job and shows the most recent execution details at a glance.
Dashboard Columns
The table contains the following columns for every recorded job:
| Column | Description |
|---|---|
| Job Name | The name you assigned to the job when it was created. Clicking the name opens the full job configuration. |
| Export Type | The export method used — for example List View, Object, CSV, Single Record, Notes, or Bulk. |
| File Type | The file format that attachments or documents are exported in — such as PDF, Original, or All Types. |
| Status | The current state of the job. See the Job Status section below for a full description of each value. |
| Last Run | The date and time of the most recent execution of this job. Blank if the job has never run. |
| Next Run | The date and time when the job is next scheduled to execute. Blank for one-time completed jobs or paused jobs. |
| Output Folder | The local directory path where exported files are saved. Manual runs are prefixed Manual_Export_; scheduled runs are prefixed Automatic_Export_, each followed by a timestamp. |
Job Status Meanings
The Status column reflects what a job is doing right now — or what happened during its last run.
| Status | Meaning |
|---|---|
| Active | The job is enabled and running on its configured schedule. It will trigger automatically at each scheduled time. |
| Paused | The job has been suspended. It will not run automatically until it is resumed. The schedule is preserved and resumes from the next interval once unpaused. |
| Running | The job is currently executing. Files are being downloaded right now. Actions other than View Log are disabled while a job is running. |
| Failed | The most recent run encountered an error and did not complete successfully. Open the job log to see which files failed and the error messages returned. |
| Completed | The job was a one-time export and has finished. It will not run again unless it is manually triggered with Run Now. |
Available Actions
Each job row has an actions menu on the right side of the table. The available actions depend on the current status of the job.
Run Now Run Now
Triggers the job to execute immediately, regardless of the configured schedule. This is useful for testing a job or performing an unscheduled export on demand. The run is recorded in the job history with the Manual_Export_ folder prefix.
Pause / Resume Pause
Toggles the active state of the job. Clicking Pause on an Active job suspends it — it will show as Paused and will not trigger automatically. Clicking Resume re-activates it. The original schedule is retained and the next run is recalculated from the current time.
View Log View Log
Opens a detailed log panel for the most recent run of this job. The log includes start and end times, total records processed, each file downloaded, any errors, and the total data size. See the Viewing Logs section for a full description of the log contents.
Delete Delete
Permanently removes the job and all its recorded history from the dashboard. This action cannot be undone. The exported files already saved to your output folder are not affected — only the job record and its log history are deleted.
Viewing Logs
Click View Log on any job to open the run log for its most recent execution. The log is a structured report that gives you full visibility into what happened during that run.
Log Contents
The log panel displays the following information for each job run:
| Log Field | Description |
|---|---|
| Start Time | The exact date and time the job began executing. |
| End Time | The date and time the job finished — either successfully, with errors, or due to a failure. |
| Records Processed | The total number of Salesforce records queried and processed during the run. |
| Files Downloaded | A list of every file that was successfully downloaded, including the file name, Salesforce record it belongs to, and the local path where it was saved. |
| Errors | Any files that could not be downloaded are listed with their file name and the error message returned — for example, permission errors, network timeouts, or missing content versions. |
| Total Bytes Downloaded | The combined size of all files successfully downloaded during the run, shown in a human-readable format (KB, MB, or GB). |
Tips and Best Practices
Check Logs After Each Scheduled Run
Even when a job shows Active, individual files may have failed due to permission changes or API limits. Review the log regularly to catch silent errors early.
Pause Before Deleting
If you are unsure whether you need a job again, pause it first. A paused job retains its configuration and log history. Deletion is permanent and the job configuration cannot be recovered.
Use Run Now for Ad-Hoc Exports
You do not need to create a separate one-time job for an unscheduled export. Simply use Run Now on any existing job to trigger it immediately. The output is saved in a Manual_Export_ folder so it does not conflict with your scheduled output folders.
Keep History Enabled in Production
For auditing and troubleshooting, it is strongly recommended to keep Job History Tracking enabled in Settings → Miscellaneous whenever the application is running unattended on a schedule.