Skip to content

Commit 47b9b51

Browse files
MJez29StalkAltan
andauthored
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 <[email protected]>
1 parent f6d69ba commit 47b9b51

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/nx-cloud/troubleshooting/ci-execution-failed.md

+2
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ Nx Cloud provides two commands to forcibly stop agents, [stop-all-agents and com
2020

2121
Once these commands are invoked, the current CI Pipeline Execution is closed and can no longer receive new work.
2222

23+
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.
24+
2325
### Nx Cloud agents were stopped due to an error
2426

2527
Nx Cloud detected a failed task in the current CI Pipeline Execution and has halted further execution.

0 commit comments

Comments
 (0)