Build Troubleshooting

Diagnose package build failures, missing artifacts, source problems, and pre-deploy command errors.

Start from the failed service package. Record the service, branch, commit, target, failing phase, and first causal log line before changing configuration.

Source Cannot Be Read

Confirm the organisation Git connection is authorised for the repository.
Re-select the repository and branch in the service configuration.
For AWS delivery connections, confirm the CodeConnection is available in the correct account and region.
Verify the commit still exists and the connected identity can read it.

Build Command Fails

Reproduce the documented install and build commands from a clean checkout.
Confirm the service source path and working directory.
Pin required runtime and package-manager versions.
Make sure required build-time variables are defined for the selected environment-file mode.
Check whether a monorepo change was excluded by watch paths or build scope.

No Artifact Is Produced

Check the target-specific output directory, Dockerfile path, static build directory, or mobile platform selection. A successful compiler exit is not sufficient if the expected artifact is written somewhere else.

Pre-Deploy Command Fails

Pre-deploy commands run during deployment, after a package exists. Keep migrations repeatable and backward compatible. Read the pre-deploy logs, confirm network access to dependencies, and verify the command uses the same environment configuration as the release.

Next Step

After correcting source or configuration, trigger a new package. Keep the failed package as evidence; do not assume a later successful build explains why the earlier one failed.