Compilation problems
The preview stopped changing
Section titled “The preview stopped changing”A visible preview may be the last successful compile. Open the diagnostics or Document health panel and address the first relevant error. Selecting a diagnostic helps you find the source location.
Check for unmatched brackets, missing quotes, or an unfinished function call. After fixing it, wait for automatic compilation or press Mod+Enter.
A file cannot be found
Section titled “A file cannot be found”Check the exact path and capitalization. Image, include, and bibliography paths must refer to files present in the project. Paths are relative to the file that contains the reference.
If you renamed a file, update its references too.
A package cannot be found
Section titled “A package cannot be found”For @local imports, verify the name and version in Local packages. Shared documents use the owner’s referenced packages; adding a same-named package to your own library does not replace them.
For @preview imports, check the version and your network connection. A package not already cached may require a download.
A font will not load
Section titled “A font will not load”Open Fonts and verify the required family and faces are available. Reconnect if a download failed, then retry. Check fonts before replacing a typeface, since different metrics can change pagination.
The exported document looks wrong
Section titled “The exported document looks wrong”Resolve diagnostics, wait for fonts, and review pending suggestions. Re-export and inspect the actual download. For a persistent problem, reduce it to a small example without private content and include the exact error and relevant source when requesting help.