Overnight scheduled flows silently skip twice a year
Your team maintains a set of Salesforce scheduled flows that run at 2 AM to prepare records for the next business day — refreshing statuses, generating summaries, and kicking off downstream automations. Twice a year, stakeholders report that the morning data looks stale or incomplete, but no errors appear in the setup logs and no flow shows a failed status. The on-call admin can't reproduce the problem on demand, and the issue clears itself by the next day. The skips appear to correlate with specific calendar dates in March and November, but the team hasn't connected the dots yet. The CTO wants a reliable fix documented before the next transition date — what architectural change do you bring to that meeting?