Flux resource "Suspended" and not reconciling in CI

By Kaveh Alemi·Latchkey

A suspended Flux resource is deliberately paused: it does not reconcile and ignores new source revisions. If CI expects a change to roll out and nothing happens, the resource may still be suspended from an earlier operation.

What this error means

flux get shows the resource as Suspended, and pushes to the source no longer trigger a deploy because reconciliation is paused.

NAME    READY   SUSPENDED   MESSAGE
apps    True    True        Reconciliation is suspended

Common causes

The resource was suspended and never resumed

Someone ran flux suspend (or set spec.suspend: true) during an incident and the resource was left paused.

suspend is set in the manifest

The manifest declares spec.suspend: true, so the resource is applied but intentionally not reconciled.

How to fix it

Resume the resource

1. Confirm the resource is Suspended with flux get.
2. Resume it (or set spec.suspend: false) so reconciliation continues.
3. Reconcile with source to apply the pending change.

flux resume kustomization apps
flux reconcile kustomization apps --with-source

Remove suspend from the manifest

If the manifest hardcodes suspend, set it to false so GitOps does not keep the resource paused.

spec:
  suspend: false

How to prevent it

• Resume resources promptly after an incident-time suspend.
• Do not commit spec.suspend: true unless you intend a permanent pause.
• Check the Suspended column in CI when a change does not deploy.

Frequently asked questions

Related guides

References

• Terraform documentation
• GitHub Actions documentation