LEARN. PRACTICE. GROW.Concept and mechanism
Flow type follows the necessary event and interaction. Screen flows collect answers during a guided experience; record-triggered flows respond to record changes; schedule-triggered flows handle time-based work without relying on a human edit. Launch point and configuration also influence access context. System context with sharing does not equal compliance with every object and field permission. API 68 documentation adds an enforced-user-context option for screen and autolaunched flows; this difference must be identified as later than the exam’s SU26 baseline without assuming availability in every org.
Guided application
Volume changes observed behavior. Avoid Get, Create, Update, or Delete Records inside loops where collections and grouped operations can be used. Moving the same element into a subflow called per record does not remove repetition. Prepare fault paths and recovery ownership, distinguishing technical failure from business approval. Debug of a record-triggered flow has reduced scope and rollback; a favorable result does not prove coexistence with every automation involved in a real save. Reproduce in a sandbox outside that mode using representative volume and permissions, and use logs to locate differences. Also confirm target version and activation, because saving or sending a flow does not establish that the intended version is running.
A flow passes with one request in Debug and fails with 170 during import. The team reproduces other automation, identifies Update Records in the loop, and prepares a collection. It then checks outcomes and errors instead of merely increasing browser waiting time.
Common pitfalls
Debug treated as production; subflow treated as a new allowance; technical error treated as approval; access context inferred only from flow name.
Related topics: Requirements, access, and platform extensions · Relationships, lifecycle, and reporting · Fields, migrations, and external data
Check event, identity, volume, and test boundaries. Recovery must match actually observed effects.
Reference: Flow Builder Debugger Considerations · Platform App Builder guide SU 26