Flow Interview

Automation 🟢 Beginner
📖 4 min read

Definition

Flow Interview is part of Salesforce's automation toolkit that allows organizations to define business logic that runs without manual intervention. It helps teams work more efficiently by automating repetitive tasks and enforcing consistent processes.

Real-World Example

a business process analyst at Nimbus Tech uses Flow Interview to standardize a business process that was previously handled inconsistently across teams. With Flow Interview in place, every record follows the same path through the workflow, ensuring compliance and reducing the back-and-forth that used to slow things down.

Why Flow Interview Matters

A Flow Interview is a single running instance of a Flow — think of it as the difference between a recipe (the Flow) and actually cooking the meal (the Flow Interview). When a Flow is launched, Salesforce creates an Interview that tracks the current position in the Flow, all variable values, and the state of any screen inputs. Flow Interviews can be active (currently running), paused (waiting for user input or a scheduled resume), or finished. This concept matters because it enables Salesforce to handle long-running processes that span multiple user interactions, scheduled wait periods, or asynchronous operations.

Understanding Flow Interviews becomes critical at scale because each interview consumes system resources and counts toward governor limits. Organizations running Record-Triggered Flows on high-volume objects can generate thousands of interviews per hour, and paused interviews persist in the system until they resume or are deleted. Admins who do not monitor and manage Flow Interviews risk unexpected governor limit errors, degraded org performance, and storage issues from accumulated paused interviews that will never resume. The Flow Interview setup page and debug logs are essential tools for monitoring interview health.

How Organizations Use Flow Interview

  • Cascade Mortgage Services — Their loan application Flow pauses after the initial data collection screen and waits for an underwriter's review. The Flow Interview persists in a paused state for up to 48 hours. When the underwriter completes the review and clicks 'Resume,' the interview picks up exactly where it left off with all previously entered data intact.
  • Nimbus Tech Support — The support manager notices that 500 paused Flow Interviews have accumulated from an abandoned escalation Flow. Each paused interview was waiting for a manager response that never came. The admin deletes the stale interviews and adds a timeout mechanism to auto-resume and close stale interviews after 72 hours.
  • Vertex Insurance — Their claims processing Flow creates thousands of interviews daily as Record-Triggered Flows fire on incoming claims. The admin monitors the Paused and Failed Flow Interviews page to identify patterns — a spike in failed interviews on Tuesday revealed a data quality issue with a batch upload that was creating claims records with missing required fields.

🧠 Test Your Knowledge

See something that could be improved?

Suggest an Edit