Known issues
This page records behavior that needs care or a verified release. A code fix under review is not a guarantee about a running service.
Sandbox pause and expiration
Pause is intended to freeze the remaining lifetime. A conflict between the node’s clock and a separate cleanup process can end a paused sandbox after its original deadline. Node-agent restart and resume of a sandbox with no expiration also need the lifecycle fix.
Until that fix has passed a live test and reached your region, do not rely on pause alone for long-term state. Save files under /data on a Persistent Volume, or store application state in a database or object storage. Host memory is not a backup. Use an explicit lifetime and release the sandbox when the task ends.
Redeploy is not rollback
lizard redeploy builds the selected source again with the current configuration. It does not select a previous build. A failed build and a failed start have different effects; inspect the active service and its logs before choosing a recovery step. Do not assume every runtime keeps the old release serving through a failed start.
Dockerfile precedence
Explicit build or start commands take priority over a repository Dockerfile. Clear those overrides when selecting dockerfilePath. A settings update can itself start a build, so check events before sending another redeploy. See Dockerfile troubleshooting.
Templates and MCP
The current Sandboxes create API accepts the two built-in templates. Instructions using lizard push for custom templates do not match the current public CLI.
Lizard Skill uses Lizard CLI. That workflow does not expose an MCP transport. Hosting your own remote MCP server is a separate application deployment; see the guide.
Service port changes: fixed and verified on 2026-09-09
The September 7 check found HTTP 503 after changing an upload service from port 3000 to 80, despite a ready process. The production fix now applies the chosen port to the running service and preserves an explicit port during upload and rebuild. A live port-change check passed on September 9. Check the public URL after a deployment as well as the service state.
Upload archives and failed-build exit codes: fixed
Lizard CLI 0.3.95 excludes macOS ._* metadata entries from source uploads and returns a nonzero exit code for failed cloud builds. Update older CLI versions; COPYFILE_DISABLE is no longer needed. The framework checks cover uploads from macOS with the current CLI.
A successful build alone does not prove the app works. Check the public URL, routes, forms, and data operations after deployment.
Updated