From 47b9b51dd3b08a0d397ead5e582a53d31b71446c Mon Sep 17 00:00:00 2001 From: Michal Jez Date: Wed, 14 May 2025 13:39:33 -0400 Subject: [PATCH] docs(nx-cloud): add tip to check for non-unique NX_CI_EXECUTION_ID on DTE failures (#27573) I ran into this issue the other day with my CI pipeline when the build number got reset Co-authored-by: Altan Stalker --- docs/nx-cloud/troubleshooting/ci-execution-failed.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/nx-cloud/troubleshooting/ci-execution-failed.md b/docs/nx-cloud/troubleshooting/ci-execution-failed.md index 91de17340c..e7d4ab1130 100644 --- a/docs/nx-cloud/troubleshooting/ci-execution-failed.md +++ b/docs/nx-cloud/troubleshooting/ci-execution-failed.md @@ -20,6 +20,8 @@ Nx Cloud provides two commands to forcibly stop agents, [stop-all-agents and com Once these commands are invoked, the current CI Pipeline Execution is closed and can no longer receive new work. +If this error occurs at the beginning of a CI Pipeline Execution it could be caused by a non-unique [NX_CI_EXECUTION_ID](/ci/reference/env-vars#nxbranch-and-nxciexecutionid) that is causing Nx Cloud to associate this CIPE with a CIPE that has already concluded. + ### Nx Cloud agents were stopped due to an error Nx Cloud detected a failed task in the current CI Pipeline Execution and has halted further execution.