helmRelease can get stuck because of different reasons

docs/monitoring.rst

@@ -62,8 +62,10 @@ body):
   ``stackspin-apps`` namespace and delete the failed job
   to silence the alert with i.e.
   ``kubectl -n stackspin-apps delete job nc-nextcloud-cron-27444460``.
+
 * **ReconciliationFailure**: A `flux helmRelease`_ could not get reconciled
-  successfully. This also happen often during initial setup phase. Use i.e.
+  successfully. This also happen often during initial setup phase. It can have
+  different root causes though. Use
   ``flux -n stackspin-apps get helmreleases`` to view the current state of
   all ``helmReleases`` in the ``stackspin-apps`` namespace.
   In case the ``helmRelease`` in question is stuck in a ``install retries exhausted``
@@ -74,6 +76,8 @@ body):
       flux -n stackspin-apps suspend helmrelease zulip
       flux -n stackspin-apps resume helmrelease zulip
 
+  Depending on the underlying cause this will fix the ``helmRelease`` state or
+  not.
   For more information on this issue see `helmrelease upgrade retries exhausted regression`_