1. - [x] Mandatory: Add the required version to the Fix version/s field.

2. - [x] Mandatory: Choose the type of documentation change or review.

• [x] We need to update to an existing topic

• [ ] We need to add a new document to an existing section

• [ ] We need a whole new section; this is a function not
  documented before and doesn't belong in any current section

• [ ] We need an Operator Advisory review and approval

• [ ] We need a z-Stream (Errata) Advisory and Release note
  for MCE and/or ACM

3. - [x] *Mandatory: *Use the following link to open the doc and find where the
documentation update should go. Note: As the feature and doc is
understood and developed, this placement decision may change:

• Published doc: GRC Troubleshooting: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/troubleshooting/troubleshooting#troubleshooting-multiline-yaml-parsing
• GRC Known Issue: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/release_notes/release-notes#policy-status-repeated-updates

4. - [x] Mandatory for GA content:

• [x] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:

• [ ] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:

• [ ] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)

• [ ] Add link to dev story here:

5. - [ ] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.

In the GRC Sync call on 09/10/2024 we discussed a problem that can still occur.  The problem is https://issues.redhat.com/browse/ACM-6063 which is a crashing pod on the managed cluster.  The crash can happen due to running out of memory which happens due to too many policy events being creating because of continual Compliance changes.  The linked Known Issue describes this problem and even gives Troubleshooting steps.  This issue is to consider moving or copying the Known Issue into the Troubleshooting document (the Troubleshooting link above is to an unrelated GRC issue – the idea is this item would be added in that same area of the doc).