---
title: "Troubleshooting basics"
description: "<p>Good troubleshooting preserves data and reduces variables."
---

> Documentation Index
> Fetch the complete documentation index at: https://planner.helpcent.re/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting basics

<p>Good troubleshooting preserves data and reduces variables. Start with observation, not deletion or repeated reconnects.</p>
<h2>Do this</h2>
<ol>
<li>Identify the affected workspace and one exact record.</li>
<li>Check local save, sync, provider, and permission status.</li>
<li>Try the same action once on a new test record.</li>
<li>Restart Planner only after pending saves finish.</li>
<li>Check for an update and review known service status if available.</li>
</ol>
<h2>Useful evidence</h2>
<ul>
<li>Planner version and operating system</li>
<li>Workspace and record title or safe identifier</li>
<li>Exact time and time zone</li>
<li>Steps that reproduce the problem</li>
<li>Visible error code or connection status</li>
<li>Whether another device shows the same state</li>
</ul>
<h2>Avoid first</h2>
<ul>
<li>Deleting the app or data directory</li>
<li>Emptying Trash</li>
<li>Repeated full imports or backfills</li>
<li>Disconnecting and reconnecting every provider</li>
<li>Sharing secrets or full private databases</li>
</ul>
<h2>Scope</h2>
<p>If only one record fails, focus on its data and relationships. If every workspace fails, focus on app, backend, account, or storage status.</p>
<h2>Good to know</h2>
<ul>
<li>Create an export before any recovery step that can overwrite state.</li>
<li>A screenshot is useful, but redact private contact and financial details.</li>
</ul>

Source: https://planner.helpcent.re/settings-help/troubleshooting-basics/index.mdx
