Monitor and Track Batch Document Jobs in Dochly
Where to monitor batch jobs
Active Jobs panel
Dochly → Batch Jobs → Active Jobs. Shows all currently running jobs with live progress, record counts, and estimated completion time.
Job History log
Dochly → Batch Jobs → Job History. Every completed, failed, and cancelled job. Click any job for the full per-record detail log.
Notification emails
Completion and failure alert emails sent to the configured admin address. Include summary stats and a direct link to the job log.
Salesforce record
Each processed record has the generated document in its Files list and any configured post-generation field updates. Spot-check individual records here.
Salesforce Reports
Build reports on the Batch_Status__c and Generated_Date__c fields Dochly writes to records. Use for pipeline dashboards and ops reviews.
Salesforce Apex Jobs
Setup → Apex Jobs. Shows all async Apex jobs including Dochly batch processing. Useful for investigating Salesforce-level queue delays.
Job status reference
Each batch job has one of five statuses at any time:
Job is waiting to start
The job has been submitted and is waiting for an async Apex worker to pick it up. For large orgs with many concurrent jobs, queuing may last 1–5 minutes before processing begins.
Job is actively generating documents
Records are being processed. The Active Jobs panel shows live progress. Percentage complete and estimated finish time update every 30 seconds.
All records processed successfully
Every record in the report was processed. A Completed status with zero failures indicates a fully clean run. The job moves to Job History.
Job finished but some records failed
The job ran to completion but one or more records could not be processed — typically due to missing data (blank email, restricted field) or template errors on specific records. Successful records have documents; failed records do not. Review the failure log and remediate failed records.
Job was stopped before completion
A user manually cancelled the job. Records processed before cancellation retain their documents. Unprocessed records were skipped.
Reading the job log
The job log is the primary tool for verifying a batch run completed correctly. Access it at Dochly → Batch Jobs → Job History → [Job Name]. Here is what a completed job log looks like:
The summary row shows total, success, failed counts, and job duration. Each record row shows the Account name, generated file name (for successes), or error reason (for failures). The error reason tells you exactly what went wrong — "Contact.Email is blank" means the signer email field was empty on that record.
Per-record status and failures
Failed records are listed in the job log with an exact error reason. The most common failure reasons and how to fix them:
The email delivery field (e.g. Contact.Email) has no value on the record. Document was generated and stored but email could not be sent. Fix: update the email field on the record, then re-run a targeted job for just the failed records using a report filtered to those specific record IDs.
The template failed to generate for this specific record — typically because a required merge field is blank or a formula field errors on this record's data. Fix: open the record, identify the problematic field, populate it or fix the template, then re-run for the failed records.
The Dochly system user doesn't have read access to a field used in the template for this record. Check field-level security and sharing rules — the running user must have access to all fields referenced in the template.
The record was deleted or merged between when the report ran and when Dochly attempted to generate the document. No action needed — the record no longer exists in the intended form.
To re-process failed records: create a new Salesforce report filtered to the specific record IDs that failed (using the Record ID IN filter), then run a new batch job against that report. This targets only the failed records without reprocessing the successful ones.
Live progress tracking
While a job is running, the Active Jobs panel shows real-time progress. The panel updates every 30 seconds — refresh the page or leave it open for auto-updates.
Progress bar (percentage complete), records processed so far, records remaining, current success and failure counts, and estimated time to completion based on current processing rate.
Click Cancel on any running job in the Active Jobs panel to stop processing. Records already generated are not deleted. The job moves to Job History with status "Cancelled" — the log shows how far it got.
Notification emails
Dochly sends notification emails at key job events — configured in Dochly → Batch Jobs → Settings → Notifications.
Sent when the job finishes — whether fully successful or with failures. Includes: job name, total processed, success count, failure count, duration, and a direct link to the full job log. Sent to the configured admin email address.
Sent immediately when any record fails during processing — does not wait for job completion. Allows prompt investigation before the full job finishes. Useful for large long-running jobs where early failure detection matters.
Batch status in Salesforce fields
When post-generation field updates are configured, Dochly writes status values to Salesforce fields on each processed record — making batch output visible in reports, list views, and dashboards.
Set to TRUE when generation succeeds for this record. Use as a prevention field for recurring jobs and as a filter for Salesforce reports showing which records have documents generated.
Populated with the timestamp when generation completed. Use in reports for time-to-generate analytics, or in formula fields to calculate days since the document was generated.
Add Document_Generated__c and Generated_Date__c to your Opportunity or Account reports to show which records have been processed in each batch run. Use as a dashboard metric: "Invoices sent this month" = count of records where Invoice_Sent__c = TRUE AND Generated_Date__c = This Month.
Build a Salesforce Flow triggered when Document_Generated__c changes to TRUE — update the Opportunity Stage, create a Task, post to Chatter, or start a downstream workflow. Batch completion becomes a trigger for the next step in your process.
Frequently asked questions
Batch job monitoring gives you full visibility into every generation run. Final guide in this series: Batch processing troubleshooting — common errors and fixes in Dochly — diagnose and fix every batch processing issue from job failures to generation errors.
Rated 5 stars · Native Salesforce app · Free to install