What is Merge History?
Merge History is a record of every PDF merge and email campaign your team has run. Each entry captures the template used, the data source, the number of rows processed, the output type, and the job status. You can use it to re-download generated PDFs, audit past operations, and track which team members ran specific merges.
History entries are team-scoped — all team members can view the full history. Only owners and admins can delete entries.
Accessing Merge History
Navigate to History in the sidebar to see the unified list of all merge and email jobs. The list is sorted by date, with the most recent jobs first.
You can filter the history by:
- Job type — PDF merge, email send, or all activity
Paginated browsing
The history list is paginated. Use the pagination controls at the bottom to browse older entries. Each page loads on demand, so even teams with thousands of past merges get fast load times.
Viewing Job Details
Click any history entry to see its details:
| Field | Description |
|---|---|
| Template name | The template used for the merge |
| PDF file | The uploaded PDF template filename |
| Spreadsheet | The data source filename |
| Row count | Number of data rows processed |
| Output type | Combined (single PDF) or Individual (one PDF per row) |
| PDF count | Total number of PDFs generated |
| Status | Completed, failed, or partial |
| User | The team member who ran the merge |
| Date | When the merge was executed |
For email send jobs, additional fields are shown:
| Field | Description |
|---|---|
| Email subject | The subject line template used |
| Emails sent | Successfully delivered count |
| Emails failed | Count of failed deliveries |
| Emails opened | Count of recipients who opened their email |
| Emails clicked | Count of recipients who clicked a link |
| Total emails | Total number of emails attempted |
Downloading Results
Individual PDFs
Open a completed job and use the Output section to download individual PDFs. Each file has a download link with a presigned URL. Click the filename to save the PDF to your device.
ZIP Archive
For merge jobs with individual output (one PDF per row), use the Download ZIP button to download all generated PDFs as a single .zip archive. The ZIP filename includes the date and job ID for easy identification (e.g., merge-2025-01-15-a1b2c3d4.zip).
ZIP availability
ZIP download is only available for completed PDF merge jobs. Email send jobs do not generate a ZIP archive. If output files have been deleted, the ZIP download will return an error.
CSV Export
Use the Export CSV option to download a spreadsheet of job item results. The CSV includes the row index, status, output filename, and any error messages for each row. This is useful for auditing which rows succeeded or failed. For email send jobs, the CSV also includes tracking columns (opened at, open count, clicked at, click count) when tracking data is available.
Job Statuses
| Status | Description |
|---|---|
| Pending | Job is queued and waiting for a worker to pick it up |
| Running | A worker is actively processing rows |
| Paused | Job was paused by a user — can be resumed |
| Completed | All rows processed successfully |
| Failed | The job encountered a fatal error |
| Cancelled | The job was cancelled by a user |
When viewing merge history, you may also see a Partial status — this indicates that some rows succeeded and some failed. Partial is a history-level status, not a job status.
Jobs in pending or running state stream progress updates to the frontend via Server-Sent Events (SSE). You can watch the progress bar update in real time.
Stale job recovery
If a worker crashes or loses connection while processing a job, the system automatically detects stale running jobs and recovers them. Stale jobs are detected based on a configurable heartbeat timeout.
Managing History
Deleting Entries
Only owners and admins can delete history entries. Deleting an entry also removes all associated output files from storage. This action is permanent — deleted files cannot be recovered.
Job Actions
For active jobs (pending, running, paused), you can:
- Pause — Temporarily stop processing
- Resume — Continue a paused job
- Cancel — Permanently stop a running job
Team members can only control their own jobs. Owners and admins can manage any team job.
Tips
- Download results promptly — Files are automatically purged based on your team’s retention policy. Download important results before the retention period expires
- Use CSV export for audits — Export job results to CSV to track which rows succeeded or failed across large merges
- Check error messages — Failed and partial jobs include error messages that explain what went wrong — use these to fix data or template issues before re-running
- Email send tracking — For email campaigns, review the sent/failed/total counts to verify delivery before sending the next batch
- Email tracking export — Export open and click tracking data as a CSV spreadsheet for reporting and analysis
Limitations
- No re-run from history — You cannot re-execute a past merge directly from the history view. Open the original template and run a new merge instead.
- ZIP download for merge jobs only — Email send jobs do not produce a downloadable ZIP archive.
- File deletion is permanent — Once output files are deleted (individually or via history deletion), they cannot be recovered.
- No version comparison — History entries reference the template at the time of the merge, but you cannot diff the template state between two history entries.