monitor-ci

Automated Nx Cloud CI monitoring uses a dedicated subagent to poll pipeline status and trigger self-healing workflows, preemptively resolving failures to reduce manual intervention and speed up feedback loops.

Self-healing workflows in CI pipelines detect states like environment issues or stalled attempts and automatically apply configured fixes. They operate within defined cycles to preemptively resolve failures without manual input.

Yes, CI monitoring automation supports configurable defaults for max cycles, timeouts, and verbosity. These settings control how long the system polls and attempts self-healing fixes before halting.

When there are no new CI attempts, the monitoring system enters a wait mode. It continues polling within the configured cycle and timeout limits until new pipeline activity is detected or limits are reached.

Yes, the monitoring orchestration handles both wait mode for stalled pipelines and auto-fix workflows for active failures. It tracks state and communicates with self-healing flows via defined actions to resolve issues.

You should halt automated CI monitoring when configured max cycles or timeouts are exceeded, or when the system provides clear user guidance indicating that self-healing flows cannot resolve the current environment issue.