Troubleshooting

When Syntic Code does not behave the way you expect, this section helps you find the cause and fix it. The pages are organized by the kind of problem you are having, from getting installed and signed in to diagnosing configuration and reading error messages. Most issues are quick to resolve once you know where to look.

How to use this section

Start with the page that matches your symptom. If syntic will not install or you cannot sign in, go to Installation and Login. If the CLI is slow, hangs, or crashes, see Performance and Stability. If Amara is ignoring your settings or memory, Debug Configuration shows you how to see what is actually loaded. For a specific message, the Error Reference lists common ones and their fixes.

Before you dig in

A surprising number of problems come from an out-of-date CLI or a stale session. Confirm you are on a current version and try a fresh session before assuming a deeper fault. Many pages here point you at the same diagnostic tools — verbose output and debug logging — because they answer most questions faster than guessing.

Getting more help

If a page does not resolve your issue, gather the details it suggests — your version, the exact command, and any debug output — before reaching out. That information turns a vague report into something that can be diagnosed quickly. The Legal and Compliance page covers licensing and terms questions, which are separate from technical faults.