Magic Merge settings let you fine-tune performance, manage notifications, control storage cleanup, and configure template defaults. Access settings from the Magic Merge app by clicking the gear icon in the navigation bar.
Control how Magic Merge processes records and generates documents. These settings affect batch sizes, parallel processing, and resource consumption.
Choose a performance profile that matches your data volume and org constraints. Each profile pre-configures the batch processing settings below.
Lower batch sizes for maximum stability. Best for large data volumes or orgs with limited resources.
Balanced performance and safety. Recommended for most use cases and typical data volumes.
Higher batch sizes for faster processing. Use with smaller datasets or during off-peak hours.
Manually configure each setting individually. For advanced users who need precise control.
When using Custom profile, configure these settings individually to optimize for your specific environment.
Controls how many parent records are grouped together in each HTML generation batch job. Higher values process more records per job but consume more CPU time. Lower values reduce per-job CPU usage but create more batch jobs overall.
Recommended: 400-700Determines the number of records processed at once during the HTML building phase. This setting affects memory usage and SOQL query efficiency. Larger batches reduce total processing time but require more memory per operation.
Recommended: 400-700Sets how many batch jobs can be submitted to the queue simultaneously. Higher values speed up large merge operations but may impact org performance for other users.
Recommended: 2-3Controls the number of parallel queueable jobs used to save PDF files to Salesforce. Increasing this value speeds up file attachment but uses more of your org's daily queueable job limit.
Recommended: 3Specifies how many individual PDF files are generated in each batch operation. Smaller batches are safer for templates with complex logic or large data volumes.
Recommended: 50-100Limits the total number of merge operations that can run at the same time across your entire org. Prevents resource exhaustion when multiple users initiate merges simultaneously.
Recommended: 3-4Maximum number of parent records that can be processed in a single merge operation.
Recommended: 10,000-15,000Maximum child records included in a single merge. Applies to the total across all child objects.
Recommended: 15,000-25,000Configure email testing and notification preferences for merge operations.
Tip: Always enable test mode when setting up a new email template or making significant changes to an existing one. This prevents accidental sends to your entire recipient list.
Monitor storage usage and configure automatic cleanup of temporary merge data.
Automatically removes old merge job batches, parent/child records, and files on a scheduled basis. This only cleans up temporary Magic Merge data and will not delete any of your Salesforce objects or records.
Warning: Disabling record deletion can cause storage to grow quickly, especially with frequent merge operations. Monitor your storage usage regularly if you enable this option.
Configure template versioning and generate starter templates based on your organization type.
Maximum number of template versions to retain per template. When this limit is exceeded, the oldest versions are automatically deleted to maintain storage efficiency. Each time you save a template, a new version is created.
Recommended: 20-30Generate pre-built templates and filters tailored to your industry. These provide a starting point you can customize for your specific use cases.
Select an industry to generate or regenerate starter templates and filters based on common use cases.
Need Help? If you're experiencing performance issues or governor limit errors, start with the Conservative profile and gradually increase settings while monitoring Apex Jobs in Setup.
