Checklist progress
0/215Learned
Platform Administrator II
Study Checklist
Checklist progress
0/215Learned
Given a complex scenario, determine the solution using the best tool or combination of tools to solve a business problem
0/11
Given a scenario, identify the appropriate tool or method for troubleshooting declarative automation
0/10
Flow tests versus Flow Debugger
Learn this conceptFlow fault paths and error emails
Learn this conceptMonitoring flow and orchestration runs
Learn this conceptDebug logs for declarative automation
Learn this conceptDeclarative automation that never ran
Learn this conceptDelayed and waiting automation diagnosis
Learn this conceptProcess Builder and workflow failure diagnosis
Learn this conceptClassic approval process troubleshooting
Learn this conceptFlow approval process troubleshooting
Learn this conceptOrchestration run details and debug modes
Learn this conceptGiven a scenario, explain the capabilities and limitations of each declarative automation tool
0/8
Understand the implications of the order of execution when using automation tools
0/10
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform Administrator II studiers. 593 members and growing.
When a Flow hits an error, usually on an element that talks to the Salesforce database, the interview fails by default, the running user sees a vague unhandled-fault message, and Salesforce emails an administrator. A fault path is a secondary route that runs only if its source element fails, so you can show a clearer message, recover, or notify someone instead of stopping with the generic error. Error emails are the main troubleshooting record of what ran, which element failed, and what data was in play.