This page reflects the current Mantra implementation and may change as the product evolves.
Schema sync
The current IDE code favors fast startup:
- load cached schema first
- check whether the server has newer data
- re-check after the app resumes from being hidden for 15 or more minutes
The schema layer then subscribes for changes instead of treating sync as a one-time import.
Code sync
Code sync is a separate path. The current Yantra client describes it as indexing Apex classes and triggers.
Full refresh
The IDE also has a full refresh path that runs schema sync, code sync, and metadata sync together. Current code marks that workflow as expensive and rate-limited, so public docs should keep the description conservative.