Schedule automatic syncs

Overview

A sync schedule refreshes your Salesforce orgs automatically, so drift comparisons, the component index and promotion insights always read current data instead of whatever was last pulled by hand. Most teams run one schedule overnight, when orgs are quiet and nobody is waiting. Schedules live in Settings → Sync Schedules. The Set up sync schedule button on the Connections page takes you straight there.

Before you start

• Connect at least one org. A schedule with no orgs runs and does nothing.
• You need the Manage sync schedules permission (sync.schedules.manage). By default Admin, Architect, Release Manager and DevOps have it. Without it you see "You have read-only access to sync schedules."
• Schedules run in the server's timezone, which is shown next to Start Time on each card.

Steps

1. Open Settings and choose Sync Schedules.
2. If you have no schedules yet, click Start With a Daily Sync of All N Orgs for a ready-made draft (02:00, every day, three orgs at once), or Build one from scratch. Otherwise click + New Schedule.
3. Give the schedule a name and set Start Time.
4. Choose Sync Mode:
   • Incremental — changed types only (recommended for daily runs).
   • Force Full Resync — every type; good as an occasional weekly run.
   • Selective types — only the types you choose.
5. Pick Syncs at Once (1–8). Higher values finish sooner but put more load on Salesforce.
6. Under Days, leave Every day selected or pick specific days. The card confirms the cadence, for example "Runs on Mon, Wed, Fri."
7. Under Orgs — Sync Order, use + Add org to schedule… to add orgs. They sync in the listed order, a few at a time.
8. Optionally attach repository fetches, so the same schedule pulls branch history once a promotion pipeline exists.
9. Make sure the Enabled switch is on, then click Save All Schedules (or Save at the top). Nothing runs until you save.
10. Check Next run on the card. To test immediately, click Run Now.

Example

Priya sets up two schedules. "Nightly incremental" runs at 02:00 every day with Syncs at Once set to 3 for acme-prod, acme-uat and acme-dev. "Weekend full resync" runs at 04:00 on Sundays only with Force Full Resync, so any missed changes are caught weekly. She saves, then checks the Activity Timeline on Monday to confirm both ran.

FAQs

Can two schedules run at the same time?

Not if they overlap. Schedules that start around the same time on overlapping days and share orgs are flagged, and saving is blocked until you change one.

What happens if an org's credentials expire?

Its scheduled syncs keep failing until it is reconnected. The Sync Center shows a red banner and workspace admins get an email. See Fix expired org credentials.

Do scheduled syncs index the org too?

Yes. Every completed sync triggers indexing automatically.

Troubleshooting

"Two schedules overlap — saving is blocked until this is resolved"

Move one schedule's Start Time, change its Days, or remove the shared orgs from one of them, then save.

A schedule is enabled but warns it would do nothing

The card says the schedule "would run on time and do nothing" when it has no name, no start time, or no orgs selected. Add what's missing, or click Keep as draft to save it disabled for now.

The schedule never seems to run

Confirm it is Enabled, saved, and that Next run shows a time. Remember the time is the server's timezone, not yours. Check Check sync and fetch status to see whether runs started and failed.

Related articles

• Run your first sync
• Selective sync and force full resync
• Check sync and fetch status
• Set up a promotion pipeline