-
Bug
-
Resolution: Timed out
-
Medium
-
Severity 3 - Minor
Summary
When using the Confluence Search with a CQL that will use a Parent page with a large number of child pages that will retrieve a lot of information (page content), it will result in the following message:
Oops, something went wrong with your search.
We could not successfully complete the search. CQL was parsed but searchManager was unable to execute searchContent. CQL: parent = "xxxx" was parsed to searchContent query due to :message was removed because it mays contain customer sensitive information
Steps to Reproduce
- Create a parent page
- Be sure to have a large number of child pages (e.g. 254)
- Try to run a Confluence Search with the filter With Parent for the specific parent page
Expected Results
Confluence should return a list of child pages, like the following example:
Actual Results
The following message is displayed:
Notes
Macros that rely on the Confluence Search will be also affected in this case. For example, the Content by Label macro, if using the With Parent filter.
Workaround
Move/reduce the number of child pages until the search properly works.
[AI-491] [Backend] Specific CQL (Confluence Query Language) Results in "message was removed because it mays contain customer sensitive information"
We encountered this issue just recently. The suggested workaround posted by Juan above seems to have work for us as well. In the meantime I voted up this issue, appears to be a bug in the "with parent" option.
I am still encountering this issue. I don't recall if this was the case when I initially submitted the ticket, but in my tests today it appears that the "With Parent" filter works sometimes, but not others. For example, when replicating the exact configuration that generated the above error, I still receive the error. However, when using other parent pages or other filter variables in conjunction with the "With Parent" filter, the macro seemed to work.
JST-331317 has been submitted.
Hi jthompson1037758669 - are you still encountering this issue?
If yes, please can you raise a support request via https://support.atlassian.com/contact/ (select Technical issues and bugs)? I've converted this issue to a bug, but reaching out via the support channel will put you in direct contact with someone to help troubleshoot.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!