Doc Batches
The Doc Batches tab is where admins run one template or bundle against many records at once, and keep an eye on the run. You need the Sliick_Docs_Admin or Sliick_Docs_Template_Author permission set to see it.
Batches run in the background, so you can leave the page and come back.
Start a new batch
Section titled “Start a new batch”-
Click New Batch.
-
On the Template tab pick a template (only published ones are listed), or switch to Bundle and pick a bundle.
-
Choose which records to include:
- By filter: in Builder (the default), pick a Field, an Operator and a value. Click Add condition for more. A record must match every condition. For date fields, Value kind lets you pick a moving date such as
TODAYorLAST_N_DAYS:30, or an exact date from a date picker. Leave the filter empty to include every record of that type. - Advanced (SOQL): if you need “or” logic or grouped conditions, switch to Advanced (SOQL) and type the condition yourself.
- By report: pick a tabular Salesforce report with up to 2,000 rows. A report with more rows is refused at Analyze and at Submit, with a message that usually gives its row count: add a filter to the report so it has 2,000 rows or fewer, or split it into smaller reports. Or click Copy these filters into the builder to start from the report’s filters and change them. Any filter that cannot be copied across is listed by name, so nothing is lost without you knowing.

- By filter: in Builder (the default), pick a Field, an Operator and a value. Click Add condition for more. A record must match every condition. For date fields, Value kind lets you pick a moving date such as
-
Set Batch size (1-200). The default is 1.
-
Pick an Output mode:
- Individual files (default): one file per record, saved on that record.
- Combined PDF only: one PDF holding every record, saved on the batch. No per-record files.
- Both (individual + combined): one file per record, plus the combined PDF.
-
If the template also makes Word files, pick an Output format: PDF (the default) or Word. Word works with Individual files only.
-
Optionally set a sort order under Sort by. See Sort order sets the page order below.
-
Click Analyze.
Check before it runs
Section titled “Check before it runs”Analyze opens a Pre-flight verdict. It tells you whether the template is ready, and how many records will be processed (a native batch has no record limit from 3.5; a premium batch takes up to 100,000 documents).
If you cannot run the template, bundle or report you picked (for example, it is not shared with you), Analyze says so with the same message Submit would give.

From here you can:
- Click Preview sample to step through up to 5 sample records and see exactly how each will look. This catches problems before you make 500 documents. If a sample cannot be shown, for example because the template only makes Word files, the preview says why.
- Click Back to edit to change something.
- Click Submit batch to start.
How big a combined PDF can be
Section titled “How big a combined PDF can be”A combined PDF is put together in one Salesforce transaction. If Salesforce cannot finish it, the batch ends with “The combined PDF wasn’t made:” and Salesforce’s message. Run it again with fewer records, or as individual documents. In Both mode the per-record files are already saved on their records, so nothing is lost. A premium batch builds its combined PDF on the premium service.
In a combined PDF, each record is its own document joined to the next, like a stapled packet. Each one keeps its cover page, and page numbers start again for every record.
Sort order sets the page order
Section titled “Sort order sets the page order”Sort by decides the order records are processed in, and so the page order of a combined PDF. Without it, records come out in roughly the order they were created, which is rarely what you want to hand someone.
- Sort by up to three fields, each ascending or descending.
- You can sort by a field on a related record, up to two steps away. For example, sort 200 Opportunities by their Account’s name.
- Records that tie on every sort field always come out in the same order, so running the same batch again gives the same packet.
- If you pick a field you cannot read, or one that cannot be sorted, you are told by name when you submit, before anything runs.
- In Individual files mode, sort order has no visible effect, since each record is its own file.
In a Flow, use the bulk action’s Sort Order input, for example Name ASC, CreatedDate DESC. Sorting a Record Ids collection inside your Flow does not change the document order. Use Sort Order. See Flow actions.

Watch it run
Section titled “Watch it run”
Open a batch to see its progress. It refreshes every 5 seconds, with a status badge, a progress bar, and a table that fills in as each record finishes. While it is running you can click Cancel batch, and Sliick Docs stops as soon as it can. If a batch looks stuck, Force complete marks it as finished, based on the records that have already succeeded or failed.
When the batch finishes, the person who started it gets a Sliick Docs Batch notification.
Download the results
Section titled “Download the results”- Individual or Both: click Download all as ZIP. For up to 50 records the ZIP is ready straight away. For more, it is built in the background and you get a notification when it is ready. You can also open each record’s file from the list. A Flow can have the ZIP made automatically: see Getting the files when the batch finishes.
- Combined or Both: the combined PDF is on the batch itself, as one download.
Retry failed records
Section titled “Retry failed records”If a batch ends as Partial Success or Failed, open it and click Retry failed. This starts a new batch for just the failed records, up to about 6,000 at a time.
If the template has been published again since the first run, the confirmation tells you, so you can choose whether to use the original version or the new one. The new batch links back to the original, so you can follow a chain of retries.
Premium batches
Section titled “Premium batches”With premium high-volume rendering on, every PDF batch, of a template or a bundle, is made on the Sliick-managed service. This includes batches from a list view and from the bulk Flow action. Word batches are still made inside Salesforce. You start, check and submit a premium batch exactly as above. What is different:
- Up to 100,000 documents per batch, with each document in a bundle counting. The pre-flight verdict shows the count, and the combined PDF size limit does not apply.
- A daily file limit warning. If the batch would use a lot of your org’s daily allowance for new files, the verdict warns you. You can still submit: delivery pauses at the limit and carries on later.
- Batch size is chosen for you. A premium batch sets its own batch size, whatever you enter.
- Files arrive as they are ready, on each record, while the batch runs. A combined PDF arrives in one or more parts of up to about 25 MB, saved on the batch and named like Monthly statements - Combined - Part 1 of 3.
- A premium panel. Expand a premium batch in the console to see how many documents were delivered, how many failed and how many are still with the service, a download link for each combined part and, once the batch has finished, when its copy on the service was deleted.
- Cancel batch stops a premium batch at its next step, usually within a few minutes, and marks it Aborted. Files already delivered stay. Records still waiting fail with a note saying the batch was aborted.
- If the service cannot take the batch when it starts, the batch ends Failed and no documents are made. The console says Premium rendering didn’t start for this batch., and the batch’s message says what to do, for example Submit the batch again later.
- Failed records say what happened and what to do. Retry failed runs them again.
- A batch that stops making progress ends on its own, about two and a half days after it started, and the records still waiting fail. You can cancel it sooner.
Resume delivery
Section titled “Resume delivery”A premium batch started by automation that runs as Salesforce’s Automated Process user (for example, a trigger on a platform event) can stall with nobody to restart it. If its files stop arriving, open the batch and click Resume delivery in the premium panel. Delivery restarts in the background from the documents the service still holds.
- Anyone who can open the Doc Batches tab and see the batch can use it.
- It appears once delivery has been idle for 15 minutes.
- It is only offered if every record reached the service. If not, the console says the batch cannot be resumed: cancel it and run it again.
- A batch a person started is never resumed this way. Cancel it and run it again.
Limits
Section titled “Limits”| Limit | Value | Can you change it? |
|---|---|---|
| Records per batch | No limit | — |
| Documents per premium batch | 100,000 (each document in a bundle counts) | No |
| Rows from a report | 2,000 | No |
| Record IDs passed from a Flow | About 6,000 | No |
| Records ticked in a list view | 200 | No, this is Salesforce’s limit |
| Records in a ZIP that is ready straight away | 50 | No, it is fixed in the package |
| Batch size | 1 by default | Yes, 1 to 200, each time you submit |
| Records in a combined PDF | No limit of ours; Salesforce’s limits apply (a premium batch’s combined PDF arrives in parts) | — |