Updated March 24, 2026
6 min read
Handle lock state and SDK errors
Map Handover error codes to clear UI states so clients and teams always understand what happened and what to do next.
Your site should convert Handover errors into clear actions for users, not technical messages.
Recognize key error codes
Important codes include HANDOVER_LOCKED, INVALID_PASSWORD, AUTH_RATE_LIMITED, STORAGE_LIMIT_EXCEEDED, and INVALID_IMAGE_TYPE.
Present user-safe messages
Map errors to plain language. Example: show Site editing is temporarily suspended instead of raw status codes.
Use fallback rendering for read errors
If content fetch fails, render safe defaults and show a lightweight admin notice. Never leave public pages blank.
Capture failure events for diagnosis
Track lock denials and upload failures in your own support logs to improve response speed and reduce repeated issues.
This page maps to packages/sdk/index.ts in the repository.