Harness "artifact ... not found" in CI

A deploy pulls its image from an artifact source (a registry connector plus a tag). "Artifact not found" means the resolved tag or path does not exist in the registry, so there is no image to deploy.

What this error means

A step fails with "Artifact not found" or "No artifact found for tag ...", often when the runtime-input tag or expression resolved to a value that was never pushed.

Harness

Artifact not found for connector 'docker-registry':
image myorg/app tag '1.4.2' does not exist in the repository.

Common causes

The resolved tag was never pushed

A runtime input or expression resolved to a tag that CI never published to the registry.

Wrong repository, path, or connector

The artifact source points at a different repository or the connector cannot see the image path.

How to fix it

Align the tag with what CI pushed

Confirm the exact image and tag CI published to the registry.
Set the artifact source tag/expression to match that value.
Re-run the deploy once the tag resolves to a real image.

Fix the registry connector and path

Ensure the artifact source uses the correct registry connector and image path, and that the connector can list the repository.

How to prevent it

Deploy only tags your CI actually pushed.
Keep artifact source image paths correct per registry.
Validate the resolved tag before the deploy step.