Project history and output
Use project history and logs to verify cloning, code updates, deployments and other operations. Repository state, task state and application availability are different pieces of information.
Review an operation
- Open the correct project and its history or logs.
- Find the operation by time and type.
- Read its status, phase and any error.
- Open the output and locate the first concrete cause of failure.
- Fix the cause and retry only after verifying the original operation.
Status meanings
| Status | Action |
|---|---|
| Queued / running | Wait and follow progress. |
| Success | Also verify the result in the application. |
| Failed | Review output and fix the cause. |
| Unknown / verification required | Treat it as neither confirmed success nor definite failure; verify the actual result. |
Do not blindly repeat a migration or data-changing command merely because the panel connection was interrupted.
Record useful information
For troubleshooting, collect the server, project, time, operation type, state and relevant output. Logs may contain sensitive values; remove them before sharing.
Use project charts alongside server monitoring. Register application file logs through custom logs.