Known issues
Check these limits before using Lizard: sandbox pause and expiration, redeploys that are not rollbacks, Dockerfile precedence, and fixed issues with the date they were verified. A fix under review may not yet apply to a running service.
Sandbox pause and expiration
connect does not resume a paused or stopped sandbox, and fork returns HTTP 409 when a volume is attached; see the sandbox lifecycle.
Pausing closes open network connections. If the processes cannot be saved, the sandbox keeps running and reports the reason in pauseError.
A pause keeps the whole disk. After a stop (kill or expiration), only files on an attached Persistent Volume at /workspace, or in a snapshot you took, remain; a snapshot holds the whole disk. Volumes use node-local storage; export files that must survive node loss. See storage and billing.
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
Template availability depends on the region and pool capacity, and the public CLI does not provide a custom-template upload flow. Check tool versions inside your sandbox. The catalog is in runtime and templates.
Lizard Skill uses Lizard CLI and does not expose an MCP transport. For MCP clients, use the hosted Lizard MCP server; see Lizard MCP. 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