Skip to content
Nx Cloud CI is in private beta 10.6× faster average CI time with 79% less compute. Join the beta
Back to Knowledge Base

Understanding "CI Execution Failed"

Nx Cloud is not aware of any more tasks to distribute. This can occur if Nx Cloud thinks it is done receiving tasks to distribute and all existing tasks have been completed.

If you are receiving this error before your full pipeline has completed, add the last target run in your pipeline to stop-after on your worker entry in .nx/pipelines/ci.yaml.

The Nx Cloud heartbeat process failed to report its status in time

Section titled “The Nx Cloud heartbeat process failed to report its status in time”

When you use Nx Cloud with your own CI provider, it spawns a background process called the "heartbeat" to keep its status in sync with your CI provider. When the heartbeat process does not report to Nx Cloud for 30 seconds or longer, Nx Cloud assumes something has gone wrong and terminates the current CI Pipeline Execution.

With .nx/pipelines/ci.yaml, the heartbeat has no off switch. To opt out, start the run with nx-cloud start-ci-run --require-explicit-completion instead of start-workers. Turning the heartbeat off makes you responsible for completing the run, so the pipeline must also run npx nx complete-ci-run as its last step, with if: always() or the equivalent for your provider. Without it the CI Pipeline Execution may never complete. See heartbeat and manual shutdown handling for the full sequence.

On Nx Cloud CI there is no heartbeat, because the run ends when the main job does.

Nx Cloud provides two commands to forcibly stop agents, stop-all-workers and complete-ci-run. The two command options are functionally equivalent, but the complete-ci-run command is preferred.

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 that is causing Nx Cloud to associate this CIPE with a CIPE that has already concluded.

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

This behavior can be disabled by setting fail-after to 0 on your worker entry in .nx/pipelines/ci.yaml.

A CI configuration file was detected, but start-ci-run does not load it

Section titled “A CI configuration file was detected, but start-ci-run does not load it”

start-ci-run exits with this error while the deprecated .nx/ci-config.yaml file exists, unless you pass --no-distribution. Migrate the file to .nx/pipelines/ci.yaml, which also maps each start-ci-run flag to a key.

nx-cloud start-workers found neither .nx/pipelines/ci.yaml nor the deprecated .nx/ci-config.yaml, or the file named by --config is missing. Add .nx/pipelines/ci.yaml and commit it. See the CI configuration file reference.

No worker-templates entry to start workers from

Section titled “No worker-templates entry to start workers from”

worker-templates is missing or empty, so start-workers has nothing to start. Add an entry.

The name passed to --workers isn't in worker-templates. Pass one of the names the error lists, or add the entry.

worker-templates has more than one entry, and start-workers ran without --workers. Pass --workers <name> to pick one.

A count such as default: 3 doesn't name a launch template. On your own CI provider, Nx Cloud has no job to take a machine setup from, so every count needs a template name, such as default: 3 linux-medium-js.

start-workers couldn't parse ci.yaml or an import from it, and the error names the file, the import, and the key. Nx Cloud reads the file at the commit of the run, so commit the fix before you rerun.

Nx Cloud was unable to start the agents workflow with the configuration in your .nx/pipelines/ci.yaml file. View the CI Pipeline Execution in the Nx Cloud UI for additional details.

Timed out after 1 hour waiting for workers

Section titled “Timed out after 1 hour waiting for workers”

Your organization was at its concurrent worker limit for an hour, so the run never got its workers. Raise the limit, or give small changes fewer workers with distribute-on changesets.

The CI Pipeline Execution ended while its run was still queued for workers, usually because a new push to the same branch replaced it or the main job finished first. Nothing needs fixing unless the pipeline ended for another reason.

Unable to get workflow status from Workers

Section titled “Unable to get workflow status from Workers”

Nx Cloud was unable to communicate with the Workers assigned to a workflow for the current CI Pipeline Execution. View the CI Pipeline Execution in the Nx Cloud UI for additional details.

The current CI Pipeline Execution had a workflow cancelled due to either:

  • a manual request in the Nx Cloud UI, or
  • a push to the same branch that already had a running workflow.

One or more workflows encountered a critical error

Section titled “One or more workflows encountered a critical error”

The current CI Pipeline Execution encountered a critical error in a child execution environment. View the CI Pipeline Execution in the Nx Cloud UI for additional details.

The current CI Pipeline Execution had at least one workflow with failed steps.

One or more workflows encountered an error

Section titled “One or more workflows encountered an error”

The current CI Pipeline Execution had at least one workflow that executed tasks which failed. See also: Workers were stopped due to an error

The current CI Pipeline Execution had at least one workflow that exceeded the timeout duration. View the CI Pipeline Execution in the Nx Cloud UI for additional details.

Last updated: