Run Asynchronously path for callouts and long-running work
Key Takeaway
Salesforce blocks callouts while a record is saving, so put them on the Run Asynchronously path of a record-triggered flow, which runs in a separate transaction after the save commits.
A record-triggered flow can include a Run Asynchronously path. The path runs in the background, in its own transaction, right after the triggering record save is committed to the database. Work that can't or shouldn't run during a save goes on this path, such as a callout to an external system or a long-running process. The work then happens without slowing down or blocking the save.
The four timing options
A record-triggered flow offers four timing options.
| When it runs | |
|---|---|
| Fast Field Updates | Before the save |
| Actions and Related Records | After the save, inside the same transaction |
| Run Asynchronously | Immediately after the record update that triggered the flow is complete |
| Scheduled path | Later, based on dates and times |
A flow optimized for Fast Field Updates can only update the triggering record's own fields. Fast Field Updates flows support only the Assignment, Decision, Get Records, and Loop elements.