GitLab CI "trigger" Errors - Child Pipeline Fails to Create

By Kaveh Alemi·Latchkey

A trigger: job should kick off a child or multi-project pipeline, but GitLab could not create it - the referenced config is missing, invalid, or the target project/ref is wrong.

What this error means

The trigger job goes red (or shows "downstream pipeline can not be created") instead of spawning a child pipeline. The parent pipeline fails because the downstream never started.

Downstream pipeline can not be created.
Pipeline will not run for the selected trigger. The rules configuration prevented any jobs from running
or the user does not have access to the downstream project.

Common causes

Child pipeline config not found or invalid

A trigger:include pointing at a missing file, or a child .gitlab-ci.yml that is itself invalid, prevents the downstream pipeline from being created.

Downstream had no jobs to run

If the child config’s rules/workflow filter out every job for that ref, the downstream is empty and cannot be created.

No access to the target project/ref

A multi-project trigger:project fails if the triggering token lacks permission, or the named branch/ref does not exist.

How to fix it

Point trigger at a valid child config

child_pipeline:
  trigger:
    include: ci/child.gitlab-ci.yml
    strategy: depend

Trigger another project correctly

1. For multi-project triggers, set project and an existing branch.
2. Ensure the child config has at least one job that runs for the target ref.
3. Confirm the pipeline’s token can access the downstream project.

How to prevent it

• Lint child pipeline configs in their own CI.
• Give child pipelines a job that always runs for the triggering ref.
• Use strategy: depend so downstream failures are visible upstream.

Frequently asked questions

Related guides

References

• GitHub Actions documentation