How do you make architectural decisions for Flow? When do you use record-triggered vs screen vs platform event-triggered flows?

Record-Triggered Flows: Fire when a record is created, updated, or deleted. Use for automation that must happen on record save without user interaction (field updates, related record creation, notifications). Before-save flows are most efficient for field updates as no additional DML is needed. After-save flows support more actions including subflows and Apex actions. Ensure flows are bulkified — avoid SOQL/DML inside loops using the Get/Update elements outside the loop.

Screen Flows: Require user interaction (data collection, guided processes, wizard-style UIs). Launch from Quick Actions, Lightning Pages, or Experience Cloud. Best for replacing custom VF pages with no-code solutions.

Schedule-Triggered Flows: Run on a scheduled basis across a batch of records. Replace Scheduled Apex for simple batch updates.

Platform Event-Triggered Flows: Subscribe to Platform Events and execute automation when events are published. Ideal for event-driven integrations and decoupled processing. Runs asynchronously. Support Resume elements for waiting on conditions.

Bulkification in Flows: Record-triggered flows process records in bulk. Use collection variables and loop-safe patterns. Avoid Get Records inside loops by collecting IDs first.