All posts
Support
Fix common translate errors: 401, 429, SMTP, and flaky networks
6 min read
Jump to section
Most user-visible failures cluster into a handful of categories. Work top-down: network, token, quota, upstream.
401 Unauthorized
- Confirm the app reached SessionBootstrap success before opening translate.
- If you cleared storage, expect a new guest; ensure the client saved the returned token.
- For web builds, verify CORS_ORIGINS includes your dev origin when using strict mode.
429 Too Many Requests
The usage gate ran and refused another increment. Inspect plan counters for the active billing period; guests hit smaller caps first. Guest 429 responses set signInToContinue: true; registered-user 429 responses use false for that flag—treat the message string as the source of truth for humans.
SMTP and OTP
Email verification requires all SMTP variables the backend config expects. Misconfigured mailers show up as 500s or timeouts during sign-up—not as mysterious translate failures.
Quick health pass
Hit /health, then authenticate, then translate a short string. If step two fails, ignore step three until auth works.