Asynchronous paths on record-triggered flows
Key Takeaway
Use an asynchronous path when a record-triggered flow needs to call an external system, because Salesforce blocks those calls while a record is saving.
An asynchronous path is an optional branch on a record-triggered flow. It runs in the background after the triggering record has been saved to the database. You use it for work that can't or shouldn't run while the record is saving, such as calling an external system or running a long operation, so the user's save isn't slowed down or blocked.
When a record-triggered flow can run
A record-triggered flow can run its logic at four different times.
| When it runs | |
|---|---|
| Fast Field Updates | Before the triggering record is saved |
| Actions and Related Records | After the save, but still during the triggering record update |
| Run Asynchronously (the asynchronous path) | After the triggering record update is complete |
| Scheduled path | In the future, based on dates and times |
A scheduled path waits a set amount of time, such as for a reminder or follow-up tied to a record's Close Date. An asynchronous path, by contrast, is meant to run right after the triggering record update is complete.