How do I resolve a Contributors Summary error?

[Ken Silz]

I'm using a Contributors Summary on one of my Confluence Spaces and I'm now getting the following message:

Error rendering macro 'contributors-summary' : For input string: ""

I tried to recreate it on the same Space as well as add it to another Space, all still display the same error message. We did recently upgrade to Premium from Standard, but not sure this is the cause. Any help on this would be appreciated.

[Shannon S · Accepted solution]

Hello everyone!

Thank you all for reporting this issue. The error relates to a known bug. If you're encountering this error, please click This affects my team on the link below.

• CONFCLOUD-71202  Contributor macro not retrieving data and throws error code 404

Thanks again, and take care,

Shannon

[Pardis Beikzadeh]

Hi Shannon,

I believe there must be more than one bug at play. The bug you linked was first reported back in 2020. I successfully configured a contributors-summary macro a couple of months ago (i.e. mid-2021). Something happened very recently that increased the impact of the bug you linked. 

If you look at the comments on that bug they are all very recent (last week or so). 

Could you please take another look to ensure there isn't something else going on?

Cheers

[Shannon S]

Hi Pardis,

Thank you for your reply. Although we raised this bug ticket last year, we're referring to it now to track the exact behavior you describe. We have encountered quite a few customers in the previous week who successfully configured the contributors macro months ago, only to have it stop working.

As a result, the ticket has been escalated as of four days ago and is now on our short-term backlog. Please make sure to add your vote and notes about your situation and we can include that in our investigation.

Thank you again, and take care!

Shannon

[Pardis Beikzadeh]

Thank you! Really appreciate the prioritization of the issue. 

[Ken Silz]

Checked my space this morning and found that the Contributors Summary bug has been resolved. Thanks Atlassian for fixing this issue so quickly!

[Mykenna Cepek]

I too am seeing this error in one of our client instances of Confluence Cloud.

I am not seeing it in our main corporate instance of Confluence Cloud. So that's a piece of data (affects some cloud instances and not others).

I narrowed it down to the "Label(s)" field. When it is blank, this error occurs. When a label is filled into that field, the error does not occur.

The problem is that most of us here do NOT want to fill in a label -- we want the macro results to include all pages (regardless of any page labels).

[Mykenna Cepek]

I encourage someone experiencing this to report it to Atlassian Support, and then post the link to the JAC bug here (not the link to your support ticket).

Normally I would have already, except it's not happening in my instance.

[Ken Silz]

That is the next step I plan to take. I think something happened on their end that screwed up the contributor summary as it was working fine without any changes made by me when the issue started.

[Mykenna Cepek]

If this affects you, please vote for it (and optionally follow to track progress) here:

https://jira.atlassian.com/browse/CONFCLOUD-71202

[Fouad Amiri]

The same thing has happened to us since last week.

[Kishan Sharma]

Hi @Ken Silz Welcome to the community.

After adding the Contributors Summary macro, have you specified the space containing the page or scope of spaces to search ? If not, can you please try it and see if that works for you. You will also need to select the page from which to calculate the contribution-based statistics. 

[Ken Silz]

Thanks for the reply Kishan. I've tried that, but I still get the same error. However, if I change it to "Current space" the summary appears again, but does not list any of the existing comments and edits in the space. See screen shots below showing the behavior I'm seeing. Keep in mind that I've had the Contributors Summary on may Overview page for a couple of months and it was working fine until one day it displayed the error message.