Comprehensive Diagnostic Articles
For step-by-step walkthroughs with error code tables, cURL test commands, and configuration examples, read our dedicated troubleshooting guides:
My database won’t connect
- Check that you selected the intended workspace before changing its settings.
- Copy the PostgreSQL connection string from your database provider. Confirm the username, password, host, port, and database name.
- Check that your database is running PostgreSQL 15+ with the pgvector extension enabled, and that the provider’s networking and SSL settings allow the connection.
- Complete the database setup step after verification so that SCHMA can prepare the tables it needs.
Review the error shown in the Studio. If credentials have changed at your provider, the saved connection may need updating. Reconnecting an existing workspace is subject to its plan’s connection policy.
My published content doesn’t appear
- Open the entry and confirm that it is published. Saving an entry as a draft does not publish it.
- Check the content type’s slug in your request. The slug can differ from its display name.
- Confirm that your API key and workspace slug belong to the workspace containing the entry.
- Check the selected environment and, if you use one, the requested locale.
- Make a fresh request from your server. If the response contains your content but the site does not, check your application’s cache or rebuild process.
My API request returns an authorization error
A 401 response usually means a credential is missing or invalid. Confirm that your request sends an Authorization: Bearer … header and the correct workspace slug.
For a 403 response, check the key’s permissions and whether the operation is available on your workspace plan. Use a delivery key to read published content. Management operations need the appropriate management permissions.
If you have rotated a key, update your server’s environment variables and restart or redeploy it. Keep API keys out of screenshots, support descriptions, and public repositories.
The AI assistant is unavailable
Check the workspace plan first. SCHMA AI features are available on Pro and Max. If you configured your own provider key (BYOK), review the key, selected provider, and model in the Studio’s AI settings.
A provider may also reject requests because of its own account limits or availability. Use the error shown in the Studio to identify the provider issue, then retry after resolving it. Your manual schema and content editing workflow remains available.
My editor can’t connect through MCP
Check that Node.js and npx are available to your editor, then verify the MCP command, SCHMA API URL, API key, and workspace slug. Restart the MCP connection after changing configuration.
Begin with a read action, such as listing content types. If reading works but writing does not, check the credential’s management permissions and the requested tool’s plan requirements.