Which flow type fits a requirement (screen, before-save, after-save, before-delete, scheduled path, schedule-triggered, autolaunched), how Flow fits the save order of execution, and how to version, secure and debug flows.
Describe capabilities, use cases, and configuration for Flow (screen flows, record-triggered flows, autolaunched flows, order of execution).
~8 min read · 21 practice questions ·
The pack unlocks every unit in the guide, reading progress, one-click practice for each topic (21 questions for this one), and unlimited timed mock exams.
| Fact | Detail | Source |
|---|---|---|
| Before-save elements | Assignment, Decision, Get Records, Loop only | |
| Before-save limits | No actions and no changes to related records | |
| Before-save position | Runs before Apex before triggers and custom validation rules | |
| After-save position | After assignment, auto-response and workflow rules and escalation rules | |
| Trigger Order range | 1 to 2,000; ties run alphabetically by API name | |
| Active versions | Activating a version deactivates the previous one | |
| Custom Error | Record-triggered flows only; message up to 255 characters | |
| Callouts | Not allowed while saving; use the asynchronous path | |
| Record-triggered default context | System context without sharing | |
| Failed and paused interviews | Automation app, Monitor tab |