Schedule a run

Last updated 26 October 2026.

A schedule makes documents on a timetable with no Flow: month-end statements on the 1st, a weekly run of certificates. It has four parts:

A template, active, that makes the document.
The records: every record of the template’s object that matches the schedule’s rules. Records it already made a document for are skipped.
A time: a start date and time in a time zone, and how often it repeats.
The person it runs as: whoever activated it, with their access. A schedule reads only what that person can see.

Each time it runs, the schedule starts a generation run in the background, like a bulk run.

A schedule in Docable named Month-end statements, on the Statement of account template with rules, marked Active: from 1 November 2026 at 06:00 Europe/London, every month on the 1st, Docable will make a PDF from Statement of account for each Account that matches your rules, skipping records it already did, running as you with your access; the next run and last run are shown. — Month-end statements: a PDF from Statement of account for each matching Account, every month on the 1st at 06:00 Europe/London, run as the person who activated it.

Before you start

To activate a schedule you need Docable Schedule Manager, given as Extra access on People and access. See Permission sets and roles.
You also hold Docable Generate and Docable Runtime Generator Storage, and can see the records the schedule should make documents for.
The template is active.

Steps

Open the Schedules tab and start a new schedule.
Give it a name people will recognise, such as Month-end statements.
Choose the template.
Set the rules that pick the records, for example accounts with a balance.
Choose the format: PDF, Word or both.
Set the start date and time, the time zone, and how often it repeats.
Check the summary. It reads the schedule back in words: what it makes, for which records, when, and as whom.
Activate the schedule. It reads Active, and shows the next run.

Example

Setting	Value
Name	Month-end statements
Template	Statement of account
Records	Each Account that matches the rules, skipping accounts already done
Format	PDF
Starts	1 November 2026 at 06:00, Europe/London
Repeats	Every month on the 1st
Runs as	The person who activated it, with their access

Watch it run

After each run the schedule shows its last run beside the next one. Open the Generation Runs tab to follow it: every run in the org is listed, newest first, with how many documents are made, the access it ran with and when it was submitted. Open a run for its documents, and choose Retry failed documents if any failed.

The Generation Runs tab: a Statement of account run, 3 of 3 made, and a Ternbrook delivery note run, 30 of 30 made.

Where the files land

Each document is kept as a Salesforce File on the record it was made for, here each account. If you send documents to your own storage, see Send documents to your own storage. Nobody signs during a scheduled run, so a signature block prints its signing line.

Check it worked

After the first run time, the schedule shows a last run. The Generation Runs tab lists the run as Made, and each matching account has its statement under Files. At the next run, accounts already done are skipped.

If it doesn’t work

What you see	What to do
You cannot activate the schedule.	Ask an admin for Docable Schedule Manager.
The run made fewer documents than you expected.	The schedule runs with the access of the person who activated it. Check that they can see the records, and check the rules.
The run stays Queued.	Background jobs wait while earlier ones finish. Follow it on the Generation Runs tab.
Some documents failed.	Open the run and choose Retry failed documents. Documents already made are kept.

Finish setup in Docable Setup schedules Docable’s own background jobs. It does not change schedules made on the Schedules tab.

Something unclear or wrong? Tell support. Product page: PDF and Word output.