Loading

Data Loader inserts or upserts cause Process Builder errors

Дата публикации: Jul 17, 2026
Описание

When using Salesforce Data Loader to perform bulk Insert or Upsert operations, a Process Builder process triggered on the affected object may fail if the batch size is too large. This occurs because Process Builder has limitations in handling high-volume bulk operations simultaneously. When a batch is too large, Process Builder cannot complete its triggered actions for all records within the allowed time, resulting in a flow trigger failure error.
Data Loader error file message:

"The record couldn't be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301j00000001X2z. Contact your administrator for help."

System Administrator flow error email example:

"An error occurred at element myRule_1_A1 (FlowRecordUpdate). UPDATE --- UPDATE FAILED --- ERRORS: (ALL_OR_NONE_OPERATION_ROLLED_BACK) Record rolled back because not all records were valid and the request was using AllOrNone header --- for SFDC record with ID: 001j0000002Xy1ZAAS"
Решение

Reducing the batch size in Salesforce Data Loader allows Process Builder sufficient time to complete its triggered actions between record saves, preventing the flow trigger timeout error.
To reduce the batch size in Data Loader:

  1. In Data Loader, navigate to Settings > Settings.
  2. Lower the Batch size value to 1.
  3. Re-run the Insert or Upsert operation.

This causes Data Loader to process records one at a time, giving Process Builder the time it needs to complete its actions. The impact on overall processing time is minimal for most datasets.

Additional Note on Batch Size

Some environments may support a slightly larger batch size (such as 20) without errors. If the error persists with a batch size of 20, set the batch size to 1.

Дополнительные ресурсы

Configure Data Loader

Номер статьи базы знаний

000387062

 
Загрузка
Salesforce Help | Article