Swantide keeps your org documentation up to date through automatic overnight syncs. You can also manually sync individual components when you need an immediate update.
Sync cadence
Initial connection: 24–72 hours to authorize the org, ingest metadata, generate AI documentation across your components, and bring the AI Assistant online with full org context.
Ongoing: nightly. Swantide picks up changes overnight, updates documentation, and refreshes the Change Log. Very large orgs can take longer than a single night to work through, so check the Last synced timestamp if you are waiting on something specific.
The Data Dictionary header shows the Last synced timestamp so you always know how fresh the data is.
What happens during a sync
All metadata components are checked for changes.
New components are ingested and documented.
Modified components have their documentation updated.
Deleted components are removed from the Data Dictionary.
The Change Log is updated with detected changes.
Your Data Dictionary and AI Assistant context are typically no more than a day behind your live org.
Manual sync: two entry points
There is no full-org batch resync button (that's intentional: a full re-ingest is heavy processing and not something you should kick off ad hoc). Instead, Swantide gives you two precise manual-sync paths for individual components.
1. Refresh a component that's already in Swantide
Use this when the component is already in the Data Dictionary and you want a fresh pull.
Open the component in the Data Dictionary.
Click Sync component in the component header.
Wait a few moments for the sync to complete.
The component's documentation, references, and change log update to the current state.
2. Sync a component that's never been ingested
Use this when the component doesn't appear in the Data Dictionary yet (recently created in Salesforce, or a metadata type Swantide hasn't pulled before).
In the Data Dictionary, click Sync Metadata.
In the Sync Metadata Component modal, pick the Component Type (e.g.,
ApexClass,StandardValueSet,GlobalValueSet).Enter the Component API Name.
Confirm, and Swantide pulls the component and generates documentation.
Tip from the modal: picklist values for standard fields are often stored as a StandardValueSet or GlobalValueSet. Pick the right type to make sure the field's values come through.
When to use manual sync
You've just deployed a change and want to verify it in Swantide.
You're in a working session and need the AI Assistant to have the latest context.
A new component isn't showing up yet and you don't want to wait for the nightly sync.
Tips
Don't wait for the next nightly sync if you only need one component refreshed. Use the per-component Sync component button.
Use the Sync Metadata modal when a component has never been ingested. The Component Type matters: picklist values often live in
StandardValueSet/GlobalValueSet.Check the Change Log to verify that recent changes have been picked up.
After a sandbox refresh, Swantide needs to re-sync the entire org. Expect the same 24–72 hour timeline as an initial connection.