Troubleshoot safety blocks
Find what you’re seeing below. Some blocks come from Syntic’s safeguards; others come from your organization’s settings, which an admin can change.
| What you see | Why | What to do |
|---|---|---|
| Amara declines to help with a request | The request looks like it breaks the usage policy | Rephrase with the legitimate purpose made clear. If the refusal was wrong, use thumbs-down and choose Refused when it shouldn’t have |
| Your account has been disabled | Access was turned off after a review | Appeal by email. See Account enforcement and appeals |
| Account unavailable | The account was deleted or deactivated | See Deleted or disabled account |
API requests fail with 403 account_disabled | The key’s owner account is disabled | The owner appeals; meanwhile use a key from an active account |
| A notice that a feature can’t be used in a HIPAA workspace | Your organization has HIPAA-ready mode on | This is by design. See HIPAA-ready mode |
| AI Memory is unavailable | An admin turned on Disable AI Memory | Ask an organization admin. See Organization admin settings |
| Failed to submit feedback | The report didn’t go through | Try again, or email support@syntic.ai |
Still stuck?
Email support@syntic.ai from your account’s address with the time, what you tried and the exact message.
Learn more
Was this page helpful?