Troubleshoot a deployment - FixCodeNow

Check status

fixcodenow list

Keep the deployment ID. FixCodeNow accepts the source before the asynchronous build and deployment complete, so a failed deployment can still have a useful ID.

Read diagnostics

fixcodenow logs <deployment-id-or-url-or-name>

Narrow the output when needed:

fixcodenow logs <target> --service api
fixcodenow logs <target> --since 30m
fixcodenow logs <target> --follow
fixcodenow logs <target> --json

Logs include build, deployment, health, and runtime evidence. Secret values are redacted.

Decide what to fix

Fix source code, dependencies, Dockerfiles, Compose configuration, commands, ports, or health checks in the repository.
Add a missing credential through the project secret controls or a private --env-file.
If the evidence points to the FixCodeNow platform, keep the deployment ID and report the redacted error instead of changing the app.

After a repository fix, run the smallest relevant local check and ship the changed source again:

fixcodenow ship . --env-file /path/to/private/fixcodenow.env

Do not repeatedly ship unchanged source. Use the existing deployment ID and logs to gather evidence first.