Swantide's Change Log tracks modifications to your Salesforce metadata over time: what changed, when, and (with the AI Assistant) what it means in plain English. Use it for auditing, debugging post-deployment issues, and team handoffs.
When to use this
After a deployment: verify what was actually changed in the org.
When debugging a new issue: see if a recent change correlates with the problem.
During team handoffs: understand what another admin or developer modified.
For compliance and audit trails: document what changed, and when.
The Change Log page (primary entry point)
The dedicated Change Log page lives in the Data Dictionary area (route /catalog/changes). It's the right starting point for "what's changed in my org recently?" questions.
At the top of the page, three summary tiles:
Changes in the selected range
Most Changed Type (e.g.,
CustomObject,Flow)Deleted Components count
Filters:
Time range tabs: 24h / 7d / 30d / Custom
Type dropdown: filter to a specific metadata type
Search: by component label or API name
Show deleted checkbox
Each change row shows the component, the type, and when the change was detected, plus two action buttons:
View diff: opens the before/after diff for that version.
Ask Swantide: opens an AI Assistant chat pre-loaded with the change context. This is the fastest way to get "what changed and why does it matter?" in plain English, so you don't have to copy the diff into a prompt yourself.
Heads up: the Change Log shows what changed and when, but does not attribute the change to a specific Salesforce user. There is no per-user column. Note also that the Change Log page's Export is "coming soon": the live CSV export is the Download CSV button in the Data Dictionary catalog view, not on this page.
Per-component Change Log (secondary entry point)
When you already have a component open, switch to its Changes tab (alongside Details and References). You'll see the same per-component timeline of changes with View diff and Ask Swantide buttons. Use this path when you're investigating one component in depth.
How change detection works
Swantide syncs metadata nightly. Changes are detected by comparing the current metadata state to the previous sync.
The Change Log captures modifications to component definitions: field changes, flow updates, Apex class edits, validation rule modifications, deletes, etc.
Changes made between syncs appear after the next nightly sync. You can also manually sync a specific component to see the change sooner (see How Often Does Swantide Sync Metadata).
Swantide stores multiple versions of each component, which is what makes the diff view and Ask Swantide possible.
Tips
Use the Change Log as a deploy validator: confirm that what you intended to deploy actually landed.
Pair with the References tab: if a component changed, check its dependents to understand the blast radius.
Troubleshooting a new issue? Check the Change Log first. A recent metadata change is often the root cause.
The diff view beats the Salesforce audit trail for understanding what actually changed in a component. The audit trail tells you something changed; the diff shows you exactly what.