> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/knowledge-base-article/triggered-pipeline-fails.md).

# Triggered pipeline fails while manual execution succeeds

Fix triggered pipeline failures that show missing service manifests or artifacts when the same pipeline succeeds manually

A triggered pipeline execution can fail while a manually run execution of the same pipeline succeeds. This topic explains a common cause and how to correct the trigger configuration.

***

## What you will learn from this topic

* How to recognize [service configuration errors](#problem) that appear only on triggered runs
* How to fix the trigger [artifact source configuration](#resolution) in `templateInputs`
* Which [fields to verify](#key-checks) so triggered runs supply the same inputs as a manual run

***

## Before you begin

* **Pipeline with a Deploy stage**: Use a pipeline that runs successfully when you execute it manually with artifact inputs.
* **Trigger access**: Open the pipeline trigger that fails so you can edit its YAML or input mapping.

***

## Problem

Triggered pipelines can fail with service configuration errors even when the same pipeline runs successfully when executed manually.

### Error messages

When you execute the pipeline through a trigger, you may see the following error messages:

```
No manifests configured in the service. manifest expressions will not work
No config files configured in the service. configFiles expressions will not work
No service hooks configured in the service. hooks expressions will not work
Failed to complete service step
```

Manual runs succeed because the Harness UI supplies the required service and artifact inputs at runtime. Triggers must provide those same inputs in configuration.

***

## Resolution

In this scenario, the artifact source configuration in the trigger is typically responsible for the error. The trigger must specify the artifact source details that you otherwise provide during manual execution.

### Fix the trigger templateInputs

Ensure that your trigger configuration includes the correct artifact source specification in the `templateInputs` section. The following example shows the required structure:

```yaml
- stage:
    identifier: xxxxx
    template:
      templateInputs:
        type: Deployment
        spec:
          service:
            serviceInputs:
              serviceDefinition:
                type: CustomDeployment
                spec:
                  artifacts:
                    primary:
                      sources:
                        - identifier: xxxxxx
                          type: xxxxx
                          spec:
                            tag: <+trigger.payload.tag>
```

### Key checks

Use the following checks when you review the trigger configuration:

* Verify that the artifact source identifier in the trigger matches the identifier configured in your service.
* Ensure the artifact tag or version is specified using trigger expressions (for example, `<+trigger.payload.tag>`).
* Check that all required service inputs are provided in the trigger `templateInputs` section.
* Compare the trigger configuration with the inputs you provide during manual execution to identify any missing fields.

After you correct the artifact source configuration in the trigger, the pipeline should execute successfully when triggered automatically.

***

## Next steps

* [Triggering pipelines](https://developer.harness.io/docs/platform/triggers/triggering-pipelines): Configure webhook, artifact, and other trigger types.
* [Artifact sources](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/artifact-sources.md): Review how artifact sources are defined on a service.
* [Artifact sources in NextGen](/continuous-delivery/troubleshooting-and-resources/knowledge-base-article/understanding-artifact-sources-in-nextgen.md): Understand NextGen artifact loading and tag behavior.

{% @harness-feedback/feedback %}