Loading

Salesforce Flow or Process Builder Error: "The Interview is too large to be saved"

Дата публикации: Apr 27, 2026
Описание

In Salesforce Flow Builder and Process Builder, a flow interview (also called the interview state) is a running instance of a flow or process — similar to how a record is an instance of an object. When Salesforce needs to pause or schedule a flow, it saves a complete snapshot of the interview — including all data the flow has processed and a history of every element executed — to the Salesforce database as a Flow Interview record.
The interview state (the size of this saved snapshot) grows:

  • Each time the flow changes the value of an sObject variable (for example, when an Assignment element updates a field on an sObject variable).
  • Each time the flow executes an element — for example, ten separate Assignment elements each with one row create a larger interview state than one Assignment element with ten rows. The same applies to multiple "Update Records" actions in a process.

If the interview state exceeds the Salesforce database limit, Salesforce cannot save the Flow Interview record. The admin who created the flow receives a flow error email with this message: "The Interview is too large to be saved."
Real-world example: A Process Builder process is configured to run scheduled actions on Opportunity records. If the process runs on a large number of records and includes multiple "Update Records" actions, the interview state may grow too large for Salesforce to save, triggering this error.

Решение

The following approaches can resolve the "Interview is too large to be saved" error in Salesforce Flow or Process Builder.

Option 1: Prevent the Interview from Being Saved

Preventing the flow from needing to save its state eliminates the issue entirely.

  • For autolaunched flows: Remove any Wait elements from the flow.
  • For screen flows: Hide the Pause button on Screen elements so users cannot pause the flow.
  • For processes (Process Builder): Remove the scheduled actions from the process.

Option 2: Reduce the Interview State Size

Redesign the flow or process so that less data needs to be saved.

  • Consolidate elements: Combine multiple Assignment elements or multiple "Update Records" actions into fewer, more efficient elements where possible.
  • Use specific lookups: In flows, make your Get Records queries as specific as possible rather than retrieving a large collection and filtering it down inside a loop.
  • Reduce loop items: For loops, reduce the number of records in the collection, reduce the number of elements inside the loop, and include only the fields in the collection that are actually needed by the flow.
  • Avoid rich text fields: Do not operate on rich text fields in flows, as they significantly increase the interview state size.

Option 3: Use Scheduled Apex

If you need a flow or process to run on a regular schedule, use Scheduled Apex to launch a flow interview for each interval. This avoids the need to save a long-running interview state.

Номер статьи базы знаний

000385514

 
Загрузка
Salesforce Help | Article