Home/Docs/Troubleshooting
Reference

Troubleshooting

Most Shipsite failures are visible states, not silent crashes. Read the lane, the artifact, the connection status, and the reservation receipt before starting a second project or a new rerun.

CURRENT PRODUCT CAPABILITIES
01

Planning never finishes

Open Studio and check whether a lane is running, stalled, or waiting on your approval. An empty evidence pack during the first minutes is expected. If there is no current stage, no remaining-time estimate, and no error, refresh once, then inspect the run record before starting another project.

Studio while planning a Pomodoro Timer site: Kuafu is assembling the first documents and a remaining-time estimate is visible.
After you enter a keyword, planning writes into Studio as it finishes. An empty library with a live lane and ETA is a real state.
02

Preview will not open

Preview exists only after a managed build has published a labeled bundle. If build is still running, wait. If a quality check blocked the bundle, open the quality-check report instead of retrying blindly. If the preview expired or is private, use the grant from Launch rather than a copied URL.

Studio Preview tab with a private access-governance note while the labeled preview is still connecting.
Preview is labeled private and not treated as live. The connecting frame is real until a completed build publishes an isolated preview.
03

An approval looks stuck

An approval waits for your decision on one document. If the document is missing, planning is not finished. If a newer document arrived, reopen it—do not approve the old badge. Dijiang cannot click approve for you.

Studio project library with the Pomodoro Timer product plan marked needs-review and your decision still required.
Open the exact product plan behind the approval before you decide. Build starts only after approval.
04

Credits look wrong

Check whether you are looking at a reservation or a settlement. Reservations sit above the final charge and return the unused portion. Automatic retries do not add a second execution service fee. A user-requested rerun does.

05

A connection will not verify

A saved secret is not a verified connection. Recreate the credential with the minimum documented scope, test it on the Connections page, and keep the last known good value if the replacement fails. Then retry the blocked task.