nx-ci-monitor

Automate self-healing for Nx Cloud CI pipelines by continuously polling CI status and spawning a ci-watcher subagent to coordinate failed attempts and retries. This reduces manual intervention and development downtime.

Monitoring failed Nx Cloud CI attempts automatically requires polling the workspace CI status and triggering a self-healing orchestration process. The system tracks in-progress, failed, and recovered attempts to resume development faster.

Yes, monitoring Nx workspace CI workflows requires a configured workspace with an nx.json file containing an nxCloudId or nxCloudAccessToken to authenticate and interact with the Nx Cloud infrastructure.

Yes, you can configure timeouts for the ci-watcher subagent during CI monitoring. The self-healing orchestration process spawns this subagent to handle failed CI attempts and requires configurable timeouts to manage recovery workflows.

Nx Cloud CI pipelines may stall during workspace builds due to transient failures or infrastructure issues. The self-healing monitor detects these stalled states, applies auto-recovery workflows, and tracks new CI attempts to resume progress.

You should not use an automated CI monitor for Nx workspaces if your environment lacks a configured nx.json with an nxCloudId, or if your system cannot spawn the required ci-watcher subagent to execute the self-healing orchestration.