Skip to content
Sojournby CloudAlgo Request early accessEarly access Request early access
Release 1 in development, 15 of 15 sprints done. Early access is open. 15 of 15 sprints done · Join early accessJoin early access
Guide

Scope and limits

What Sojourn does not do, where it runs, and the limits to know before you rely on its numbers.

Salesforce admin About 5 minutes Since release 1

Sojourn measures how long records spend in the values of the fields you track, and with each owner. This page lists what it leaves out on purpose, the editions it runs on, how it behaves when your org changes, and the limits we know of.

What Sojourn does not do#

  • It is not an audit trail. Sojourn records only the Tracked fields you choose, and its Intervals can change after they are written: Reconcile and the Health Monitor's repairs close and correct them, and the Sojourn Health Monitor permission set can edit and delete them. Keep Salesforce's own field history for who changed what, on every field.
  • No long text or rich text fields. The field picker offers picklists, lookups, checkboxes, dates, and short text fields; formulas, auto-numbers, and long text are not offered.
  • No setup objects. User, Group, and the other setup objects cannot be tracked; see Track an object.
  • No export to other systems. Sojourn makes no callouts and sends nothing out of your org. Your data leaves only when you take it: by exporting a report, or with the CSV files a purge attaches to its run.

How Sojourn records a change#

Sojourn records each change inside the save that makes it, through its own triggers on Case, Lead, and Opportunity and through a capture Flow on any other object. It uses no Platform Events and no Change Data Capture, so nothing waits in a queue and changes arrive in the order they were saved. Its work counts toward the Salesforce limits of that save, and it leaves a share of each limit for your own automation; see Tune the advanced settings. When Sojourn cannot record a change, the save still succeeds and the Error Log gets a row.

Editions#

Sojourn runs on Salesforce Enterprise, Unlimited, Performance, and Developer Edition, in Lightning Experience. Professional Edition is not supported yet. See Check the prerequisites.

Encrypted fields#

Sojourn copies a Tracked field's values onto its Intervals, and no Interval field is encrypted, so a field you encrypt with Shield Platform Encryption is stored in plain text there. For such a field, keep only the change; see Encrypted fields in Track an object.

When your org changes#

  • Records are merged. The Intervals of a record merged away stay with it and are not moved to the record that remains; see When records are merged.
  • An owner is deactivated. Deactivating a user does not change the owner of their records, so their owner stays remain open and keep counting until each record moves to someone else. Reassign the records when the person leaves. The breach alert template emails only active users: a record owned by an inactive user sends no alert, and an inactive manager is left off (see Email a breach alert).
  • A queue is deleted. Before you delete a queue, set it to Use the next rule on the Business hours screen and choose Save, which removes its business hours row. If you delete the queue first, the screen no longer lists it, its row in Queue Business Hours stays unused, and an exported settings file still carries it, so an import in another org skips it with "Queue ... not found in this org." Intervals the queue held keep its name.
  • The org's time zone changes. Sojourn counts days in the org time zone: the Day summary rows, Rebuild summaries, and the purge cutoff. Rows written after the change use the new zone, and rows already written keep their old day boundaries. To count past months again in the new zone, use Rebuild summaries (see Summaries); a month a purge has cut into cannot be rebuilt. The minutes on each Interval do not change.
  • Opportunities use more than one currency. The Opportunity Amount on an Interval is not converted; see Opportunity amounts in more than one currency.

People and records Sojourn has to handle#

  • Integration and API-only users. Sojourn records every save of a Tracked object, whoever makes it, and the person saving needs no Sojourn permission set. Changed By on each Interval names the user. Sojourn has no setting yet to leave out one user's changes; Records to track and Record types on the object's Records tab limit which records are tracked (see The Records tab), and Pause lets a bulk load run without Sojourn's work (see Pause capture during a bulk import).
  • Person Accounts. Not tested yet. A Person Account is an Account record, so tracking one means tracking Account, on the Plus plan, through a capture Flow. Try it in a sandbox first.
  • Experience Cloud guests. The timeline shows to signed-in site users only; guest users cannot see it. See Show the timeline on a record.

Known limits#

  • Breach and warning flags on open stays change when the Live values job runs. Between runs, an open stay past its goal shows no flag yet, and without Live values scheduled, stays are flagged only when they close. See Run the jobs.
  • Closed by a checkbox. When Closed when reads a checkbox, a record that closes only through that checkbox, with no change to a Tracked field, gets Record Closed at its next tracked change or at the nightly Reconcile, unless the checkbox is itself a Tracked field. See When a record closes.
  • Interval sharing and the timeline. Setting Interval to Private limits reports and list views only. The timeline follows the record's own sharing. See Who sees which Intervals.
  • A retried Case update. Rarely, when Salesforce retries a bulk Case update after refusing one Case in it, a status or owner change your own automation made in that update goes unrecorded until the Case's next change, or until the nightly Reconcile records the value that changed without capture.
  • The archive is not in reports. Archived Intervals show on the timeline and can be read with SOQL from Apex and the API, but reports cannot read them. See The archive.
  • Volume. We have measured Sojourn in scratch orgs, up to 72,003 Intervals, not yet at millions; see Reports at large volume.

You are done when you know which of these apply to your org, and the fields you track hold nothing that some readers of Intervals may not see.

Updated in release 1 This page changes in the same pull request as the feature it describes.