Snapshots & rollback#

The platform's safety guarantee: nothing is a one-way door.

The snapshot gate#

Before Forge Load writes, it captures a snapshot — the pre-image of every record it's about to change. The snapshot is taken first; the write is gated on it. So at any point after a load, the state it changed from is recorded.

Rollback#

Rolling back a load restores its snapshot:

• An update rollback restores the prior field values.
• An insert rollback removes the inserted records.
• A delete rollback recreates the deleted records and re-maps their ids.

Conflict awareness#

Rollback is three-way aware. If a record changed again after your load (by someone else), a blind restore would clobber that change. Instead, Forge detects the conflict and surfaces it rather than silently overwriting — you decide.

One write path#

Forge Patterns, SOQL Studio writes, and Forge Configure deploys all compile down to a managed load. That means there is exactly one write path in the platform, and it's the snapshotted, reversible, conflict-aware one — every write inherits the safety net.

Note: Connector deletes confirm the record is actually gone (read-after-delete), so a rollback never reports success for a delete that didn't happen.