Docs should cover how to respond to Manifest generation error (cached)

[jsoref]

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

Manifest generation error (cached) doesn't lead to users being able to fix the error.

To Reproduce

1. Migrate from argo-helm argo-cd 5.6.8 (with a old style CMP) to argo-cd 5.7.0 (without properly configuring a replacement CMP)
2. Try to get the CMP to work by setting up a CMP for conf

Expected behavior

• When there's an error about manifest generation (cached), there should be enough information somewhere to explain how to flush the cache (this could be in the form of Documentation, the FAQ, or in the GUI, or probably all of the above).

Screenshots

Version

{
    "Version": "v2.4.11+3d9e9f2",
    "BuildDate": "2022-08-22T09:13:16Z",
    "GitCommit": "3d9e9f2f95b7801b90377ecfc4073e5f0f07205b",
    "GitTreeState": "clean",
    "GoVersion": "go1.18.5",
    "Compiler": "gc",
    "Platform": "linux/amd64",
    "KustomizeVersion": "v4.4.1 2021-11-11T23:36:27Z",
    "HelmVersion": "v3.8.1+g5cb9af4",
    "KubectlVersion": "v0.23.1",
    "JsonnetVersion": "v0.18.0"
}

Logs

Paste any relevant application logs here.

[jsoref]

For people wondering, and as guidance to someone working to fix this:

---

1. Clicking the teeny tiny down arrow next to ↻ Refresh will yield a menu:
   
2. Clicking Hard Refresh on the App will clear any cached content for the app and should give things a chance to reproduce

---

Notes:

1. There should be a tooltip for Hard Refresh explaining what it does
2. Any log view that shows a cached warning should include a note explaining how to trigger a hard refresh to clear the cached item.

[simonfelding]

agree. this is very confusing, thanks for writing an explanation.

[x45dev]

For people wondering, and as guidance to someone working to fix this:

1. Clicking the teeny tiny down arrow next to ↻ Refresh will yield a menu:
   
2. Clicking Hard Refresh on the App will clear any cached content for the app and should give things a chance to reproduce

Notes:

1. There should be a tooltip for Hard Refresh explaining what it does
2. Any log view that shows a cached warning should include a note explaining how to trigger a hard refresh to clear the cached item.

Agree - thank you for posting this! I can't believe how much time I wasted because of this. :(

[ForbiddenEra]

What about when you're adding a new app and there's no existing app to hard refresh?!

[mrhankeh9934]

this doesnt fix it

[francovp]

What about when you're adding a new app and there's no existing app to hard refresh?!

Someone know this? I have the same problem :(

[crenshaw-dev]

Manifest generation error (cached) just means that there was an error when generating manifests and that the error message has been cached to avoid runaway retries.

Doing a hard refresh (ignoring the cached error) can overcome transient issues. But if there's an ongoing reason manifest generation is failing, a hard refresh will not help.