Harness "Input set ... not found" in CI

Input sets supply the runtime input values a pipeline needs. "Input set not found" means the run referenced an input set identifier that does not exist in the pipeline's project/org scope, or on the git branch when Input Sets are stored in git.

What this error means

A triggered or API-started run fails with "Input Set with identifier '...' not found" and the pipeline does not execute because required inputs are unresolved.

Harness

Invalid request: Input Set 'prod_inputs' not found for pipeline 'deploy'
in project 'app', org 'default'.

Common causes

The input set identifier is wrong or was deleted

The run references an input set id that does not exist in the pipeline scope, or it was renamed/removed.

The input set lives on a different git branch

For git-stored input sets, the referenced branch does not contain that input set file.

How to fix it

Reference an existing input set

List the pipeline's input sets and confirm the exact identifier.
Update the trigger/API call to reference a real input set.
For git-stored sets, target the branch that contains it.

Provide inputs inline instead

If no input set applies, pass the runtime inputs directly in the run request or trigger payload.

How to prevent it

Keep trigger/API input set references in sync with existing sets.
Avoid renaming input sets that triggers depend on.
For git experience, reference the correct branch for input sets.