Schedule a Batch Document Run in Salesforce with Dochly

Invoices always go out on the 1st of the month. Renewal notices always go out on Mondays. No one forgets, no one is on holiday — the schedule runs regardless.

The Get Records query inside the Flow re-runs at each scheduled trigger — so this month's closed deals automatically become this month's invoices, without updating any filter manually.

Schedule large batches at 6 AM before business hours. Processing during off-peak hours avoids API limit collisions with user activity and reduces the risk of a large run affecting system performance during the working day.

Add a completion or failure email step to the Flow (checking Dochly: Get Batch Status) so your team knows the run finished successfully — or immediately knows if something went wrong — without having to check manually.

Native Flow frequency. Runs every day at the configured Start Time. Best for: compliance document generation or any workflow where documents need to be generated every business day. Use with relative date filters like "Today" or "Yesterday" in the Get Records element.

Native Flow frequency, recurring on the day of week matching the Start Date. Best for: renewal notice batches, weekly account statement generation, or any document that goes out on a fixed weekly cadence.

Not natively selectable. The common pattern is a Daily-triggered Flow with a Decision element at the start that checks whether today matches the day of month you want (e.g. Day = 1), and exits without calling the bulk action on every other day.

For patterns Flow's scheduler can't express directly — first business day of the quarter, last Friday of the month, every 6 hours — pair the Flow with a Scheduled Apex class (System.schedule with a CRON expression) that invokes the Flow. This requires an Apex developer or admin comfortable with cron syntax.

Add a checkbox field (e.g. Invoice_Sent__c) to the object. Add it to your Get Records filter as Invoice_Sent__c = FALSE. After the bulk action call succeeds (checked via Dochly: Get Batch Status), update Invoice_Sent__c = TRUE on the processed records. On each run, only records with the field still FALSE are included — already-processed records are automatically excluded.

For monthly cycles, reset the prevention field at month-end: a separate Salesforce Flow triggered on the 1st of each month sets Invoice_Sent__c back to FALSE for all Closed Won records with a CloseDate in the previous month. This makes them eligible for the next run without manually managing the field.

Setup → Flows → [Flow] → Deactivate on the active version. The Flow stops triggering but the configuration is preserved. Reactivate when needed — the next trigger is calculated from the reactivation time based on the Frequency and Start Time you configured.

Flows are versioned. Clone the active version, make your changes (schedule, filters, template), save as a new version, then Activate it — this automatically deactivates the previous version. You cannot edit an active version in place.

There's no "Run Now" button for a Schedule-Triggered Flow. To trigger an ad hoc run, open the Flow in Flow Builder and use Debug — this runs it immediately without affecting the next scheduled trigger.

Salesforce doesn't provide a built-in execution log for Schedule-Triggered Flows. Instead, every bulk action call creates a DH_Generation_Batch__c record with Total/Completed/Failed/Cancelled/Status — build a report on that object to audit that the schedule ran correctly and at the expected times. For failed Flow interviews (not batch failures), check Setup → Flows → [Flow] → Paused and Failed Flow Interviews.