How long Jenkins waits after catalog install or upgrade for this Helm operation to settle. First the named catalog operation (chartActionOutput → GET catalog.cattle.io.operations metadata.state) must leave Steve transitioning without error. Then the Helm app summary.state (including pending-upgrade / pending-rollback) and helm-owned objects on the app (relationships). Default 300 seconds. Must be greater than zero (empty uses the default). The same timeout also bounds ClusterRepo index refresh when catalog reports the chart is missing.

A leftover failed or deployed summary from before this catalog call is not the result yet. A failed operation (helm-pod exit not 0) fails the build immediately with that kstatus message and the tail of the Helm job log (Steve operation /logs, same as Recent Operations → Logs). A long log is truncated so exit code: N and the ending Error: / FAILED stay visible. An empty 2xx log body is marked helm job log was empty (not a bare exit code alone). 404 leaves only kstatus; other log HTTP errors add a short cannot-read note with status. Jenkins does not wait on a missing app. Settled app failed fails the build even if workloads still look active (cluster serving). Settled ready with a Deployment/StatefulSet that never becomes active also fails the build. HTTP GET paths are debug (Verbose logging). Console INFO is state and object changes of this operation.