From 7f0f14a12f2e2cbf648f53e14a136ee89645b4e6 Mon Sep 17 00:00:00 2001
From: Kent Japhet Ballon <kballon@gitlab.com>
Date: Mon, 22 Jan 2024 22:07:10 +0000
Subject: [PATCH] Update troubleshooting for failed trigger jobs

---
 doc/ci/pipelines/downstream_pipelines.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/ci/pipelines/downstream_pipelines.md b/doc/ci/pipelines/downstream_pipelines.md
index ae2ca74e6f819..668337f4ea273 100644
--- a/doc/ci/pipelines/downstream_pipelines.md
+++ b/doc/ci/pipelines/downstream_pipelines.md
@@ -804,6 +804,12 @@ With multi-project pipelines, the trigger job fails and does not create the down
   to run pipelines against the protected branch. See [pipeline security for protected branches](index.md#pipeline-security-on-protected-branches)
   for more information.
 
+To identify which user is having permission issues in the downstream project, you can check the trigger job using the following command in the [Rails console](../../administration/operations/rails_console.md) and look at the `user_id` attribute.
+
+```ruby
+Ci::Bridge.find(<job_id>)
+```
+
 ### Job in child pipeline is not created when the pipeline runs
 
 If the parent pipeline is a [merge request pipeline](merge_request_pipelines.md),
-- 
GitLab