Skip to main content

​
Artifact troubleshooting

Use this guide when a FORGE build appears complete but the expected downloadable output is missing or unusable.

​
No artifact appears

Check whether the build actually reached PACKAGING and completed packaging successfully. A build can finish generation/validation work and still fail while creating or uploading the artifact.

​
Artifact status failed

Inspect packaging/upload error metadata, storage health, size limits, and worker state. If many unrelated artifacts fail at the same time, investigate storage/platform health rather than retrying each build independently.

​
Download denied

Confirm:
  • current account/organization context
  • project/resource permission
  • artifact ownership
  • credential scope for Developer API downloads
  • artifact has not expired or been deleted
Possession of the artifact ID is not authorization.

​
Download is corrupt or incomplete

When Starfire provides a checksum, calculate the checksum of the downloaded file and compare it. If the checksum differs, retry the supported download path and investigate transport/storage issues. If the checksum matches but the project itself is broken, the problem is in the packaged content rather than download integrity.

​
Artifact expired

Check the plan/organization retention policy. If no retained copy exists, create a new build from the correct source revision when necessary.

​
Missing files inside artifact

Compare the artifact file list with the intended packaging configuration and build workspace. Not every temporary workspace file necessarily belongs in the output.

​
Secret discovered in artifact

Rotate/revoke the secret immediately. Then fix the build/project configuration so future artifacts contain placeholders instead of credentials.

Download & verify artifacts

Review the normal artifact download and verification workflow.