---
schema_version: "1"
id: 2d9f3740154c83e437a0d4516f7fa0637a448914a80fb863781d38e0e0d3976f
title: Record-Triggered Flow Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_considerations_trigger_record.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_considerations_trigger_record.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4a4e10c6c0e6a31a521fc1f34fd6eb4f77d629cbdc4e54eea0ec4c8f54e6b2e6
description: A record-triggered autolaunched flow makes additional updates to the triggering record before or after it’s saved to the database. Understand the considerations and special behaviors of flows that make before- and after-save updates.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Record-Triggered Flow Considerations

A record-triggered autolaunched flow makes additional updates to the triggering record before or after it’s saved to the database. Understand the considerations and special behaviors of flows that make before- and after-save updates.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr></tbody></table>

## General Considerations

These considerations apply to any record-triggered flows.

- Record-triggered flows run custom validation rules.
- You can’t reference a screen flow from an autolaunched flow.
- Due to their position in the order in which they run, record-triggered flows can behave differently from similar workflow rules.
- A flow can't look up an account when a user creates a case from that account if the Case.AccountId field is read only for the running user. For example, when a user creates a case from an account detail page, the Case.AccountId field remains null. The case doesn’t automatically link to the account, so the flow can't use the unpopulated Case.AccountId field to look up the Account record.
- A record-triggered flow fails if it attempts to access external data, such as Data Cloud objects, during its synchronous run path. It fails because Salesforce prevents callouts to external services from running while a record is saving. To run flow logic that queries an external data source, use an asynchronous path. On the Start element of your flow, turn on the **Add Asynchronous Path** toggle under Actions and Related Records to create this path. The asynchronous path runs in the background after the original record save is successfully committed, enabling the external callout.
- Asynchronous paths don’t support the `ISCHANGED` operator, for example in decision elements.
- Flows that are configured to run on a given object don’t run if that object has a formula field referencing another object and that field is updated on the other object.
    
    For example, consider a record-triggered flow that runs for updated accounts. The Account object contains two custom formula fields:
    
    - Partner Address: A formula field that references the Address field on another account record.
    - Contact Phone: A formula field that references the Phone field on a contact record.
    
     
    | Scenario | Result |
    | --- | --- |
    | The Address field on the second account record is updated. | The flow is triggered for both the second account record and the account record that references the Address field. |
    | The Phone field on the contact record is updated. | The flow isn't triggered, even though the account record that references the Phone field now shows the updated data. |

## Considerations for Fast Field Updates

These considerations apply to record-triggered flows that are optimized for fast field updates (before-save).

- The flow can’t perform actions other than updating the triggering record’s field values.
- The flow can’t update values in records that are related to the triggering record.
- Only these elements are supported: Assignment, Decision, Get Records, and Loop.
- The View All Data permission is required to activate an autolaunched flow that has a trigger.

This video explains when to use fast field (before-save) updates and when to update actions and related records.

View this [video](https://play.vidyard.com/xxvrx6bZu6rSVwUYLdbANB?) in a separate tab.

## Considerations for Debug Mode

- The `ISCLONE()` formula function always evaluates to `FALSE` when you’re in debug mode. For example, if a record-triggered flow contains an `ISCLONE()` formula function in the entry criteria or in the Decision element, `ISCLONE()` evaluates to `FALSE` even when you’re debugging with a cloned record.

#### See Also

- [Before-Save Record-Triggered Flows](https://help.salesforce.com/s/articleView?id=platform.flow_concepts_trigger_record.htm&release=264.0.0&type=5 "Creating or updating a record can trigger a record-triggered flow to make additional updates to that record before it's saved to the database. A record-triggered flow can update a Salesforce record 10 times faster than a record-change process. Configure the record trigger in the Start element of your record-triggered flow.")
- [_Apex Developer Guide_ : Triggers and Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm)