Runbooks
Step‑by‑step guides for common operational issues.
Last updated: 2026-03-17
Last reviewed by: Compliance team
These runbooks are designed to resolve common problems without support.
Runbook: Deploy failed
- Open Deployments → Logs
- Identify the first failure line
- If missing envs → add env vars in Settings → Environments
- If build failed → verify lockfiles and build command
- Redeploy
Runbook: Preview URL loads but app errors
- Check Runtime logs
- Verify
PORTusage and bind to0.0.0.0 - Confirm
startcommand is correct - Restart runtime
Runbook: Custom domain not working
- Open Domains tab
- Verify domain is attached to correct environment
- Check DNS records and wait for propagation
- Confirm SSL status is Issued
Runbook: DB provisioning failed
- Check plan eligibility (Pro/Enterprise)
- Check quotas in Billing usage
- Retry provisioning from project banner
- If still failing, rotate admin credentials and retry
Runbook: Credits not applied to invoice
- Open Settings → Credits and confirm balance
- Check billing policy allows credits for plan charges
- Wait for next invoice cycle
Runbook: Marketplace payout delayed
- Open Marketplace → Payouts (seller) or Easy‑Forge (admin)
- Check payout profile status (complete + verified)
- Confirm payout is not paused by admin risk control
- Verify payout status logs and FX conversion rate
Runbook: Buildpacks build failed
- Open build logs and find the first buildpack error
- If stack mismatch → use supported builder image
- If buildpack missing → ensure buildpack image exists in registry
- Redeploy after adjusting buildpack config