Watch Sojourn in the Health Monitor
See whether field tracking works, what failed, why it failed, and the step that fixes it.
The Health Monitor tab in the Sojourn app shows whether field tracking is working right now. It is separate from Sojourn Settings, so a support or operations group can watch Sojourn and fix its errors without changing its configuration.
Who can open it#
Give people the Sojourn Health Monitor permission set; the Sojourn Admin permission set includes it. Without either, the tab says which permission set is needed and loads nothing. Health Monitor users can create the missing Interval, ignore, or resolve any error. Fixes that change configuration open Sojourn Settings, so for Health Monitor users without Sojourn Admin the page says "Ask a Sojourn admin" instead.
Overview#
- The banner reads Healthy, Needs attention, or Not working, with one line that says what needs you. Check again reads everything afresh.
- Capture lists what stops Intervals being recorded: tracking off for the whole org, a Tracked object whose capture Flow is missing or cannot be read, a paused object or one waiting for Catch up, a failed backfill.
- Jobs shows whether Live values and Reconcile are scheduled, their last run, and the next one.
- Errors counts the errors that need you, those in the last 24 hours, and those fixed in the last 24 hours, by type.
- Recent errors lists the latest, each with its fix.
Errors#
The Errors tab lists Error Log rows by status, type, object, and age. Select rows to Create intervals, Mark resolved, or Ignore them together. Open a row to see what happened, why, how to fix it, and the technical details for support.
| Type | What happened | How to fix it |
|---|---|---|
| Limit | The save that changed the record was already close to a Salesforce governor limit, so Sojourn stepped aside to protect it. | Choose Create interval, or leave it: the nightly reconcile retries Limit and DML errors older than an hour, up to three times. If many come from one import, pause the object before the next import and catch up after it. |
| DML | Salesforce refused to save the Interval, often because of a validation rule, a required field, or another app's trigger. | Fix the cause the technical details name, then choose Create interval, or let reconcile retry it. |
| Config | A Tracked field names a field that was deleted or renamed, or that Sojourn can no longer read. | In Sojourn Settings, remove the field or choose its replacement, then mark the error resolved. |
| Business hours | No usable business hours applied, so calendar minutes were recorded as business minutes. | Choose default business hours in Sojourn Settings, or hours on the Tracked object, then mark the error resolved. |
| Unknown | Sojourn hit an error it did not expect. The user's save still went through. | Choose Create interval. If it happens again, send the technical details to CloudAlgo support. |
Create interval records the change at the time it happened and marks the error Resolved. It is refused when later changes to the same field were already recorded, because the change can no longer be placed; ignore the error, or run a History backfill to rebuild the record's history.
The same Create Interval action is on every Error Log record page.
You are done when
- The banner reads Healthy, or every item it lists has a fix under way.
- No error in the Errors tab reads Needs you without a reason you know.
Updated in release 1 This page changes in the same pull request as the feature it describes.