Level: AdvancedSalesforce

Salesforce Flow Interview Questions: Advanced Automation (Part 17)

7 min read
Salesforce Flow Interview Questions featured image: advanced automation

Salesforce Flow Interview Questions go beyond the basics and test how you build, test and fix real automation. This is Part 17 of our 25-part series, with advanced questions on screen flows, orchestration, testing, performance and migration.

In Part 2, we covered flow types, elements and the order of execution. Here we go deeper. Our flow types guide, fault paths guide and Migrate to Flow guide will help.

How to Use These Salesforce Flow Interview Questions

First, build one screen flow and one record-triggered flow in your practice org. Next, break them on purpose and fix them with debug and fault paths. Then answer the scenario questions, because senior rounds use them to test real design choices.

Salesforce Flow Interview Questions diagram showing design, build, test, then deploy
How Salesforce Flow Interview Questions build up: design, build, test, then deploy and watch.

Salesforce Flow Interview Questions on Migrating to Flow

Study with Migrate to Flow.

  1. Why did Salesforce retire Workflow Rules and Process Builder?
  2. What is the Migrate to Flow tool?
  3. What can the tool not migrate?
  4. How do you plan a migration of many processes?
  5. Should you merge many old processes into one flow?
  6. How do you test a migrated flow?
  7. What happens to time-based workflow actions during migration?
  8. How do you turn off the old automation safely?
  9. What is the difference between a migrated flow and a rebuilt flow?
  10. How do you document what each old process did?
  11. Scenario: an object has 6 Process Builders and 4 Workflow Rules. How do you migrate them?
  12. Scenario: after migration, emails go out twice. What do you check?

Screen Flow Design Questions

Study with Flow Types.

  1. What makes a good screen flow?
  2. What are reactive screen components?
  3. Define conditional visibility on a screen.
  4. What is a Data Table component?
  5. How do you show a record lookup on a screen?
  6. How do you validate input on a screen?
  7. What is a custom screen component, at a high level?
  8. How do you add a screen flow to a record page?
  9. How do you launch a screen flow from a button?
  10. Can you run a screen flow in an Experience Cloud site?
  11. What is the pause element, and when do you use it?
  12. How do you pass a record ID into a screen flow?
  13. How do you show a progress indicator in a screen flow?
  14. Explain how you pass data from a screen flow back to a record page.
  15. What are flow screen sections and columns?
  16. Scenario: users skip important fields on a long screen. How do you redesign it?
  17. Scenario: a guest user must submit a form on a site through a flow. What do you check?

Salesforce Flow Interview Questions on Record-Triggered Flow Design

Study with Order of Execution.

  1. When do you use a before-save flow instead of an after-save flow?
  2. What is the Flow Trigger Explorer?
  3. How do you set the order of many flows on one object?
  4. What is $Record__Prior used for?
  5. How do you stop a flow from running in a loop?
  6. What are entry conditions, and why do they matter?
  7. How do you run a flow only when a field changes?
  8. What is an asynchronous path?
  9. What is a scheduled path?
  10. How many record-triggered flows should one object have?
  11. What is the “Run Asynchronously” path used for?
  12. How do you skip a flow during a data load?
  13. What is a custom permission, and how can a flow check it?
  14. Scenario: two flows on Opportunity update the same field. How do you fix the conflict?
  15. Scenario: a flow must call an external system after save. Which path do you use?

Flow Orchestration Questions

Study with Approval Processes.

  1. What is Flow Orchestration?
  2. What are stages and steps?
  3. Define an interactive step.
  4. What is a background step?
  5. What is an evaluation flow?
  6. How do users see their orchestration work items?
  7. When is orchestration better than an approval process?
  8. What licences or limits apply to orchestration, at a high level?
  9. How do you assign an orchestration step to a queue?
  10. How do you report on orchestration progress?
  11. Scenario: onboarding needs HR, IT and the manager to act in order. How do you design it?
  12. Scenario: one step of an orchestration is stuck. How do you find out why?

Salesforce Flow Interview Questions on Testing and Debugging Flows

Study with Fault Paths.

  1. How do you debug a flow?
  2. What is a flow test?
  3. Which flow types support flow tests?
  4. What is a fault path?
  5. What is a fault email?
  6. Who receives flow error emails?
  7. How do you read a flow error message?
  8. What is the Flow Error Log, at a high level?
  9. How do you test a flow as another user?
  10. What is a custom error message in a flow?
  11. How do you test a flow with many records at once?
  12. What is a flow interview?
  13. How do you see paused flow interviews?
  14. Scenario: a flow works in debug but fails for one user. What do you check?
  15. Scenario: users see “An unhandled fault has occurred”. What do you do?
Salesforce Flow Interview Questions diagram showing Flow compared with Apex
Flow compared with Apex in Salesforce Flow Interview Questions.

Performance and Limits Questions

  1. Why should you never put a Get Records element inside a loop?
  2. What does bulkification mean for flows?
  3. How many records can one flow transaction handle, at a high level?
  4. What is a CPU time limit error?
  5. What is the Transform element?
  6. How do you update many records with one element?
  7. When should you use a collection filter?
  8. What is the difference between a Loop and a Transform element?
  9. How do you avoid hitting DML limits?
  10. What is the Collection Sort element?
  11. What is the Assignment element used for in bulk updates?
  12. How many elements can one flow run in a transaction, at a high level?
  13. Scenario: a data load of 10,000 records fails because of a flow. What do you change?
  14. Scenario: a flow is slow on save. How do you make it faster?

Salesforce Flow Interview Questions on Versions and Deployment

Study with Sandboxes and Change Sets.

  1. What is a flow version?
  2. How many versions can a flow have?
  3. Can you edit an active flow version?
  4. How do you deploy a flow with a change set?
  5. Does a deployed flow arrive active or inactive?
  6. How do you roll back to an older version?
  7. How do you document a flow?
  8. What is a flow naming convention?
  9. How do you compare two flow versions?
  10. How do you deploy a flow with DevOps Center?
  11. Scenario: a bad flow version went live. How do you fix it fast?
  12. Scenario: a flow uses a hard-coded record ID. Why is this a problem in deployment?

Flow vs Code Questions

Study with Admin vs Developer.

  1. When should you use Flow instead of Apex?
  2. When is Apex the better choice?
  3. What is an invocable action?
  4. How can a flow call Apex?
  5. Can Flow call an external API?
  6. What is an HTTP Callout action in Flow, at a high level?
  7. How do admins and developers share an object safely?
  8. What is an Apex action in Flow?
  9. How do you call a flow from Apex, at a high level?
  10. What is a Lightning web component in a flow screen?
  11. Scenario: a developer wants to replace your flow with a trigger. How do you decide?
  12. Scenario: a business rule changes every month. Flow or code?

Salesforce Flow Interview Questions FAQ

Are advanced flow questions asked for admins?

Yes. Flow is now the main automation tool, so experienced admins get several deep flow questions.

Do I need to know Flow Orchestration?

Know what it is and when to use it. Deep detail is asked only for automation-heavy roles.

Official Resources

Quick Recap

  • These Salesforce Flow Interview Questions cover migration, screen flows, triggers, orchestration, testing and limits.
  • Use before-save flows for field updates on the same record.
  • Never put Get Records or Update Records inside a loop.
  • Add fault paths to every flow that changes data.
  • Next, practise finding and fixing common problems.

What’s Next?

Continue with the next part. Read Salesforce Troubleshooting Interview Questions for Admins (Part 18).