关于通过Data Loader回溯更新记录无法触发Flow的技术求助

Let’s walk through the most common reasons your batch updates aren’t firing your Flow, along with how to troubleshoot each scenario:

• Your Flow’s trigger settings don’t match the update action
  Double-check your Record-Triggered Flow’s configuration:

  • Is the trigger event set to "A record is updated" (not just "created")?
  • Does the entry criteria align with the changes you’re making via Data Loader? For example, if your Flow only triggers when Status__c changes to "Approved", make sure your CSV is actually updating that field to the correct value (and that the previous value wasn’t already "Approved").

• You’re using Data Loader’s Parallel Batch API mode
  Salesforce’s Parallel Batch API (the default for large batches) skips record-triggered automations like Flows and Apex triggers to prioritize performance. Switch to Serial Batch Mode in Data Loader’s settings—this forces updates to run one at a time, which will trigger your Flow as expected. Just note this will be slower for large datasets.

• Your Flow is in Draft mode (not activated)
  It sounds obvious, but it’s easy to miss: make sure you’ve clicked the Activate button on your Flow. Draft Flows won’t run for any record changes, including Data Loader updates.

• The Flow’s run context or permissions are blocking it

  • If your Flow runs in User Context, the account you’re using for Data Loader needs full read/write access to the records you’re updating, plus any fields referenced in the Flow. Check sharing rules and profile permissions to ensure there’s no access restriction.
  • If you’ve set up a Start Condition that limits the Flow to specific users or profiles, confirm the Data Loader user falls into that group.

• Your update doesn’t actually modify the fields required to trigger the Flow
  Salesforce only triggers record-based Flows when the update changes a field that’s part of the Flow’s entry criteria or trigger conditions. If your CSV is updating fields that aren’t tied to the Flow’s trigger logic, or if the field values don’t change (e.g., setting a field to the same value it already has), the Flow won’t fire.

• You’re using the wrong Flow type
  Make sure you’re working with a Record-Triggered Flow, not a Schedule-Triggered, Autolaunched, or Screen Flow. Only Record-Triggered Flows fire automatically when records are created or updated—other types need manual or scheduled initiation.

内容的提问来源于stack exchange，提问作者Hermes Omar Gomez