Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-67848

Blog post macro fails with "error: Failed to get macro details" when loading a lot of results

      Issue Summary

      Environment

      any

      Steps to Reproduce

      1. Create a new page in a space that has at least ~300 blog posts
      2. In that page, add a "Blog Posts" macro
        1. Ensure that "Content Type to Display" is set to "entire" (the default)
        2. Increase "Maximum Number of Blog Posts" to at least 300
      3. Optionally, publish

      Expected Results

      Blog Posts macro should show results, at least partially with a "Load More" button.

      Actual Results

      • If the macro takes over a minute, it fails with "error: Failed to get macro details".
      • If the macro takes less than a minute but more than 20 seconds, it fails with "Error: Rendering this content exceeded the timeout of 20 seconds."

      Notes

      Workaround

      None really. If intending to search all blog posts on a single page, you can use the built-in search functionality.

            [CONFCLOUD-67848] Blog post macro fails with "error: Failed to get macro details" when loading a lot of results

            Atlassian Update - September 8, 2021

            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!

            Sunny Xu (Inactive) added a comment - Atlassian Update - September 8, 2021 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!

            @Andrew Macheret can you please help me move this along?  It seems that it's just sitting here waiting to be assigned.

            Rory Apperson added a comment - @Andrew Macheret can you please help me move this along?  It seems that it's just sitting here waiting to be assigned.

            Hi all, please do whatever is possible to get this resolved soon, as it should have been resolved originally instead of https://jira.atlassian.com/browse/CONFCLOUD-65459.  The reason https://jira.atlassian.com/browse/CONFCLOUD-65459 was created was directly from a support case I opened, https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-445432, because of this specific issue with blog post macro timing out.

            The priority on this issue is currently "low" whereas the priority on https://jira.atlassian.com/browse/CONFCLOUD-65459 is/was "high".  Why is this low when that one was high?

            https://jira.atlassian.com/browse/CONFCLOUD-65459 was opened in January of this year, and I waited until just recently to get it fixed, only to find that it didn't actually fix the issue, which was why this issue here was opened.

            To summarize:

            1. I created support ticket https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-445432   because of the specific issue with blog post macro timing out.
            2. Giuliano de Campos worked with me on that and ultimately opened https://jira.atlassian.com/browse/CONFCLOUD-65459 from it (as mentioned in the ticket).
            3. https://jira.atlassian.com/browse/CONFCLOUD-65459 was "resolved" after 9 months, but it did not resolve the issue with the blog post macro – behavior unchanged.
            4. This issue here (https://jira.atlassian.com/browse/CONFCLOUD-67848) was opened because of the fact that the blog post macro was not fixed when https://jira.atlassian.com/browse/CONFCLOUD-65459.
            5. This issue is set to low priority.

            Does this mean I'll have to wait at the very least 9 more months before the issue is actually resolved??  This is a very disruptive problem and has affected how I do my job, and as I pointed out multiple times in all these places, the blog post macro never timed out when we were on "server" – only when we came to "cloud".  It immediately did not work when we came to "cloud".

            Thank you for your considerations.

             

            Rory Apperson added a comment - Hi all, please do whatever is possible to get this resolved soon, as it should have been resolved originally instead of https://jira.atlassian.com/browse/CONFCLOUD-65459 .  The reason https://jira.atlassian.com/browse/CONFCLOUD-65459 was created was directly from a support case I opened,  https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-445432 , because of this specific issue with blog post macro timing out. The priority on this issue is currently "low" whereas the priority on https://jira.atlassian.com/browse/CONFCLOUD-65459 is/was "high".  Why is this low when that one was high? https://jira.atlassian.com/browse/CONFCLOUD-65459 was opened in January of this year, and I waited until just recently to get it fixed, only to find that it didn't actually fix the issue, which was why this issue here was opened. To summarize: I created support ticket https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-445432    because of the  specific issue with blog post macro timing out. Giuliano de Campos worked with me on that and ultimately opened https://jira.atlassian.com/browse/CONFCLOUD-65459 from it (as mentioned in the ticket). https://jira.atlassian.com/browse/CONFCLOUD-65459 was "resolved" after 9 months, but it did not resolve the issue with the blog post macro – behavior unchanged. This issue here ( https://jira.atlassian.com/browse/CONFCLOUD-67848 ) was opened because of the fact that the blog post macro was not fixed when https://jira.atlassian.com/browse/CONFCLOUD-65459 . This issue is set to low priority. Does this mean I'll have to wait at the very least 9 more months before the issue is actually resolved??  This is a very disruptive problem and has affected how I do my job, and as I pointed out multiple times in all these places, the blog post macro never timed out when we were on "server" – only when we came to "cloud".  It immediately did not work when we came to "cloud". Thank you for your considerations.  

            "Blog Posts macro should show results, at least partially with a "Load More" button." – I would be clicking "load more" for hours, as I have literally thousands of blog posts I'd like to see all at once.  I don't mind waiting 2 or 3 minutes for them all to load.  When our site was on "server" before we migrated to "cloud", it would take around 45 to 60 seconds to load the entire 3000 or so entries on one page.

            Rory Apperson added a comment - "Blog Posts macro should show results, at least partially with a "Load More" button." – I would be clicking "load more" for hours, as I have literally thousands of blog posts I'd like to see all at once.  I don't mind waiting 2 or 3 minutes for them all to load.  When our site was on "server" before we migrated to "cloud", it would take around 45 to 60 seconds to load the entire 3000 or so entries on one page.

            Andrew Macheret added a comment - https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-445432

              Unassigned Unassigned
              amacheret Andrew Macheret
              Affected customers:
              4 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: