Checklist progress
0/316Learned
Platform App Builder
Study Checklist
Checklist progress
0/316Learned
Given a scenario, demonstrate the use of formula fields to meet stated business requirements.
0/15
Given a scenario, determine the capabilities, use cases, and implications of roll-up summary fields.
0/9
Given a scenario, demonstrate the use of validation rules to meet stated business requirements.
0/14
Create and configure flows using Flow Builder
0/21
Describe the capabilities and use cases for Flow Approval processes
0/13
Given a scenario, determine the appropriate flow type to meet stated business requirements
0/5
Maintain, monitor, and troubleshoot flows
0/11
Testing flows with the Flow Builder debugger
Learn this conceptAutomated flow tests in Flow Builder
Learn this conceptFlow version activation and interview continuity
Learn this conceptFlow version deletion constraints
Learn this conceptFault paths for flow error handling
Learn this conceptUnhandled flow fault notifications
Learn this conceptTransaction rollback after a flow error
Learn this conceptGovernor-limit failures versus fault paths
Learn this conceptPaused and failed flow interviews
Learn this conceptFlow Trigger Explorer for record-triggered flows
Learn this conceptRecursive record-triggered flow loops
Learn this conceptDescribe the capabilities and use cases for using Agentforce to automate business processes
0/9
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform App Builder studiers. 592 members and growing.
A record-triggered flow starts because a record is being saved. If that flow then creates, updates, or deletes a record, Salesforce runs the save sequence again on the affected record, which can start more record-triggered flows in the same transaction. Those chained saves share one CPU and governor budget, so a loop of flows can exhaust limits even when each flow looks simple.