You are here:
Considerations for Orchestrations
Keep these considerations in mind when designing and using orchestrations.
Required Editions
| View supported editions for Flow Orchestration. |
Entry and Exit Condition Requirements
Resources selected for a requirement for a step entry condition or a stage or step exit condition can contain orchestration resources or global variables. There are limitations for what can be included in a requirement.
- To use a record for the Resource or Value fields, you must select a field on the record.
- The referenced record must use fields from its object, not fields from a related record.
Record-Change-Triggered Flow Orchestration Events
A requirement for a step entry condition or a stage or step exit condition can contain a reference to a record. Changes to that record can trigger the orchestration to evaluate the status of the current stage and the outstanding steps within it. There are limitations for when the record can trigger condition evaluations.
- The referenced record’s parent object must support change events.
- The referenced record fields aren’t IsDeleted, SystemModeStamp, or any field that’s derived from a related record or a formula.
- The referenced record is null or has an invalid ID.
- The referenced record is a global variable in an autolaunched orchestration.
- The referenced record is a global variable other than $Record in a record-triggered orchestration.
Input Values for Flows
If the combined input values for a flow called by an orchestration step is more than 32,768 characters, the orchestration fails. This error can be caused by passing one or more records to a flow called by a step. To avoid this error, pass a record ID to the referenced flow, and use a Get Records element in the flow with the passed ID. Using a passed ID with a Get Records element also means that you always have the latest version of the record.
If the combined input values for a flow called by a flow approval process step is more than 32,768 characters, the flow approval process fails. This error can be caused by passing one or more records to a flow called by a step. To avoid this error, pass a record ID to the referenced flow, and use a Get Records element in the flow with the passed ID. Using a passed ID with a Get Records element also means that you always have the latest version of the record.
Email Notifications
When a flow called by a step fails and causes an orchestration to fail, two email notifications are sent.
- A flow error notification
- An orchestration error notification
