Every Salesforce admin eventually meets the scheduled Flow — the one that runs at midnight, updates a thousand records, and either quietly saves the team hours or quietly creates a mess nobody notices until Monday. Scheduled Flows are powerful precisely because nobody watches them run. That is also what makes their timing decisions so important.
Here are five timing decisions worth getting right before you activate a scheduled Flow.
1. Pick the right start time, not just a convenient one. A Flow that updates opportunities at midnight competes with nightly integrations, data loads, and backup windows. If another job locks the same records, your Flow fails or queues behind it. Check what else runs overnight — ask your integration owner, check scheduled Apex jobs — and pick a window with breathing room. A 2 AM run that finishes cleanly beats a midnight run that collides.
2. Decide what "every day" really means for your records. A daily scheduled Flow re-evaluates its entry criteria each run. If a record still meets the criteria tomorrow, it gets processed again — which is fine for a reminder, but dangerous for an update that should happen once. Use a flag field, a date stamp, or a "processed" checkbox so repeat runs skip records already handled. Idempotency is the unglamorous habit that prevents duplicate tasks, duplicate emails, and duplicate Chatter posts.
3. Batch size is a design decision, not a default. Scheduled Flows process records in batches, and a Flow that works on fifty test records can hit governor limits on fifty thousand. Keep the per-record work lean — avoid nested loops, avoid SOQL-like lookups inside loops, and move heavy logic into subflows only where it genuinely helps. Test with a realistic volume in a sandbox before you trust the Flow in production.
4. Handle failures where nobody is watching. A record-triggered Flow fails loudly in front of a user. A scheduled Flow fails in a log. Add a Fault Path to every data element, log failures to a custom object, and notify an admin group when something goes wrong. Our guide to sending custom notifications with Flow walks through the no-code setup, and it matters twice as much for jobs that run while everyone sleeps.
5. Know who the Flow runs as. Scheduled Flows run in system context by default, which means they bypass sharing rules and field-level security the running user would normally hit. That is usually what you want for a nightly job — but it also means a Flow can update records a human could not. Review the run-context behavior before you activate, not after an audit asks about it — see our explainer on Flow run context for the details.
One last habit: schedule a monthly review of every active scheduled Flow. Business rules change, fields get repurposed, and a Flow that was correct in January can be wrong by October. A fifteen-minute review beats a month of silent bad updates.
Scheduled Flows reward admins who think about time as a design input, not an afterthought. Pick a quiet window, make runs repeat-safe, keep batches lean, catch failures loudly, and know your run context. Do that, and the midnight job becomes the most reliable member of the team.
Originally published at Way2Force — practical guides on Salesforce Flow, automation, and CRM.
Top comments (0)