Loading

OmniScript Save for Later — Considerations and Limitations

Date de publication: Mar 2, 2026
Description

The Save for Later feature allows users to save an in-progress OmniScript and resume it at a later time.

Saved sessions are stored as:

  • OmniScriptSavedSession (Standard OmniStudio Data Model)
  • OmniScriptInstance__c (Custom Vlocity Data Model)

When a user selects Save for Later, the system stores the current OmniScript state along with runtime metadata. When the user resumes the session, the OmniScript reloads using the saved data.

Saved sessions are tied to the OmniScript definition version that was active at the time the session was created. If an OmniScript is deactivated and reactivated, previously saved sessions don’t resume as the same instance. Instead, a new OmniScript instance is created. Older saved instances remain stored in the system.

If Merge Saved Data JSON into Updated OmniScript is enabled and the Save Object Id (or ContextId) matches across versions, saved data can prefill the updated OmniScript. A new instance is still created.

User behaviour differs depending on authentication type:

  • Guest users operate in a shared context without authentication. Saved sessions and related attachments are accessible within the guest context.
  • Community users are authenticated. Saved sessions are private and accessible only to the original user and administrators.

 

Save for Later isn’t designed for collaborative editing. Editing the same saved session by multiple Community users can lead to data inconsistencies

Save for Later for Guest Users is only Supported in Custom Vlocity Data Model and not supported in Standard OmniStudio Data Model.

Résolution

Review the following limitations and considerations when implementing Save for Later.

Unsupported configurations

Save for Later isn’t supported for:

  • OmniScripts that contain other OmniScripts (directly or indirectly)
  • FlexCards with embedded OmniScripts
  • OmniScript flyout windows containing OmniScripts
  • OmniScripts embedded inside custom LWCs

When using Child (Reusable) OmniScripts:

  • Only steps and actions are copied to the Parent.
  • Setup configurations, including Save for Later settings and styles, aren’t inherited.
  • Save configuration must be defined on the Parent OmniScript.

Set Error element values aren’t persisted because they aren’t stored in Data JSON.

Payload size limitation (Affects Managed Package Runtime Only)

Save for Later fails if the total request payload exceeds 4,194,304 characters (4 MB).

The payload includes:

  • Data JSON
  • OmniScript definition metadata
  • Transform data
  • File metadata (if applicable)
  • Additional runtime information

Because of this, the network payload can be significantly larger than the visible Data JSON.

Possible error messages include:

  • “Save for Later failed…”
  • “Max message parameter length is 4194304 characters”

To avoid failures:

  • Reduce nested structures
  • Minimize large JSON nodes
  • Remove unnecessary transforms
  • Avoid large file attachments
  • Break large OmniScripts into smaller flows

Multiple Community users editing the same session

Editing and saving the same session by multiple Community users isn’t supported. If a second user edits and saves a session created by another user, data inconsistencies or save errors can occur when the original user resumes.

Only the original user (and administrators) should edit a saved session.

Known issue: Session status not updating after completion

In some scenarios, after completing a resumed OmniScript, the saved session status remains In Progress, allowing potential resubmission.

Workaround:

Use DataRaptors to extract the saved session record and update the status from In Progress to Completed.

Numéro d’article de la base de connaissances

005314262

 
Chargement
Salesforce Help | Article