Skip to content

Fix slow performance or crashes

Updated View as Markdown

Performance problems can come from a large note, attachment transfer, provider run, plugin, rendering path, or background migration. A precise case is more useful than a generic reinstall.

Do this

  1. Note the action, workspace, record, and time of the slowdown or crash.
  2. Restart after saves complete and reproduce once.
  3. Disable the one recently added plugin or integration if the problem clearly began there.
  4. Check CPU, memory, storage, and pending sync.
  5. Collect the supported diagnostic report and review it before sharing.

Large records

A single huge note, table, attachment set, or imported transaction batch can reveal a local bottleneck. Test a small record in the same workspace.

Plugins and integrations

Disable one suspected source at a time. Do not uninstall and erase its data until you know whether you need it for diagnosis or recovery.

Crash loops

If Planner crashes at launch, preserve the data directory, record the installed version, and use the supported safe or recovery path from release guidance.

Good to know

  • Do not send unredacted system logs that contain private paths or record content.
  • Repeated retries can make a metered provider or import problem worse.
Planner.li
Help and documentation for Planner.li.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close