Sanity service issues: sync transaction, certificate errors - how to report?
ServerError: unable to sync transaction result to search storefirst certificateand
leaf certificateerrors when running scripts against our datasets. If there's no obvious issue, is there a way to report it other than here?
Those errors sound frustrating! Here's what you need to know:
Check the Status Page First
Sanity maintains a status page at status.sanity.io where you can check for any ongoing incidents or maintenance. This should be your first stop to see if there's a platform-wide issue affecting the search store or API services.
About These Errors
The "unable to sync transaction result to search store" error typically indicates an issue with Sanity's internal search indexing system. When you make changes to documents, those changes need to be synced to the search store for querying. This error suggests that sync process is temporarily failing.
The certificate errors ("first certificate" and "leaf certificate") are SSL/TLS-related issues that could stem from:
- Network connectivity problems between your scripts and Sanity's API
- Outdated Node.js versions with older SSL libraries
- Corporate proxies or firewalls interfering with SSL handshakes
- Expired or misconfigured certificates (though this would typically be on Sanity's end if it's affecting multiple users)
The combination of both error types suggests there might be a broader infrastructure or connectivity issue.
How to Report Issues Properly
Beyond posting in the community forum, here are the official channels:
Contact Page: Visit sanity.io/contact where you can access account support for technical issues, billing, and other concerns
Email Support: Reach out to support@sanity.io with details about your errors
For Paid Plans: If you're on a Growth or Enterprise plan, you typically have access to priority support channels with guaranteed response times
What to Include When Reporting
When you contact support, include:
- The full error messages and stack traces
- Your project ID and dataset name
- Timestamps of when the errors occurred
- Your Node.js version
- Whether this affects all operations or specific queries/mutations
- Network environment details (corporate network, VPN, etc.)
If the status page shows no incidents and you're experiencing these issues, definitely reach out to support directly as they can investigate your specific project and environment.
Show original thread4 replies
Was this answer helpful?
Sanity – Build the way you think, not the way your CMS thinks
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.
