Skip to main content

Data History

Jetstream keeps a local history of the data modifications you make, so you can always go back and see exactly what you changed, when, and what the results were — including the loaded records and per-record success/failure files.

History is captured for:

  • Load Records (including retries and trial runs)
  • Load Records to Multiple Objects
  • Update Records Without a File and Bulk Update From Query
  • Query results edits (inline table edits and bulk edits)
  • Record modal saves (create, edit, clone) and Create records without a file

Loading Custom Metadata records is not captured — those loads are deployed through the Metadata API rather than the data APIs. Use the download options on the results screen to keep a copy.

Open Data History from the clock icon in the header, the Load Records menu, or the home page.

Your data stays on your device​

info

Data History is stored locally on this device — in your browser's private storage (or the desktop app's local storage). It is never sent to the Jetstream server.

This also means clearing your browser's site data permanently deletes your history. Download anything you need to keep long-term.

In most browsers, Jetstream automatically asks for "persistent storage" to protect your history from automatic cleanup — no action needed on your part. Firefox shows a permission popup instead of granting this silently, so there Jetstream skips the automatic request — use the Keep My History button on the Data History page (or in Settings) to grant it yourself.

Viewing and downloading history​

Each entry records the org, feature, object(s), operation, status, and record counts. Depending on the feature, the detail view lets you preview or download:

  • Input Data — the records that were submitted (file-based loads and mass updates)
  • Request — exactly what was sent to Salesforce (loads to multiple objects, query result edits, and record saves)
  • Output Data — per-record success/failure, including error messages

Tabular data can be downloaded as CSV, Excel (XLSX), or JSON, so you can re-load it or archive it anywhere you like; payloads that are not tabular are downloaded as the stored JSON file.

Retention, pinning, and limits​

History is cleaned up automatically: the oldest entries are removed as new ones are saved. Pin any entry to exclude it from automatic cleanup.

Limits depend on your plan — free plans keep your 15 most recent entries for up to 60 days, while paid plans (and the desktop app, browser extension, and Jetstream inside Salesforce) keep unlimited entries for up to a full year.

Settings​

From the Settings page you can:

  • Turn Data History off entirely (a per-load "don't save" option is also available on each load screen)
  • Adjust how long history is kept (paid plans)
  • Choose where history is stored — including a real folder on your computer (Chrome/Edge and the desktop app), where files are visible, backed up, and survive clearing browser data
  • See how much storage your history is using
  • Delete all saved history from the device

Notes​

  • When Jetstream runs inside Salesforce (canvas), history is stored per Salesforce domain and is more likely to be cleared by the browser — use the web or desktop app for a durable history.
  • History is per-device: your history on one computer is not visible on another.