How big are Kernel sync batches in Salesforce?
Last updated: June 22, 2026
Kernel Salesforce sync and backfill jobs run in batches of 200 records.
That does not mean Kernel can sync only 200 records. It means Salesforce processes the job in 200-record chunks until the full record set is complete. For example, a 1.2 million Account backfill is roughly 6,000 batch chunks, so it can take a while.
What this applies to
Backfilling
Kernel_Account__clinks for Accounts.Async Salesforce record sync jobs.
Large Account cohorts where Kernel is creating or updating Salesforce records in the background.
What to expect
The job should appear in Salesforce Apex Jobs or the relevant Kernel sync history.
Large org-wide jobs can keep running after the setup screen or browser tab is closed.
Processing time depends on Salesforce queue load, org automation, field permissions, validation rules, triggers, and record count.
Some records can fail while the rest of the batch job continues.
Good to know
The 200-record size is a Salesforce Apex batch scope, not a Kernel API limit.
A large total record count is normal for an initial backfill.
Re-running the Kernel Account backfill is safe for already-linked Accounts. It focuses on Accounts that still need a
Kernel_Account__cback-link.If the job is slow, check whether the subscriber org is doing extra work on Account or Kernel Account writes.