02 · Record-triggered flows done right

Build one alongside the video: tight entry conditions, before-save vs after-save, and the update that cannot recurse.

Entry conditions are your governor limit

A flow that fires on every edit of every Account is a tax on the whole org. Entry conditions keep it to the records that matter — set them first, always.

Before-save when you can

Before-save flows update the triggering record with no extra DML and run an order of magnitude faster. Reach for after-save only when you must touch other records.

Practice in your org

• Open your Developer Edition org and follow along step by step
• Change one thing at a time and note what happens
• When something breaks, read the error before searching for it