Confluence Cloud instances with no add-ons functioning

[David Benson]

We've had reports of over 10 Confluence Cloud production instances where no Connect add-ons are working correctly. When they ask Atlassian support they are getting the answer "We're currently upgrading our cloud infrastructure to make your Atlassian experience even better" which I think translates to there's a duff build in the wild, but it'll be fixed in the next release cycle.

This is causing us a high support load, as initially users think it's our add-ons. This combined with no public statement from Atlassian on the issue makes it hard to convince users we're not at fault. What is the plan/schedule to fixing these instances?

Thanks, David

[Maarten Arts]

initially users think it's our add-ons. This combined with no public statement from Atlassian on the issue makes it hard to convince users we're not at fault.

This seems to be a recurring topic lately. It would be great if Atlassian would take some responsibility in these cases. 

[David Benson]

The fix has started rolling out for this, I believe yesterday. From what I know there's a build of Confluence Cloud in production where Connect fails to initialize with:

3/wiki/atlassian-connect/all.js:1 Cannot decode passed ui params

In the console. Atlassian have told me that the next ACJS version fixes the problem, and is due to be rolled out in the next 2 weeks. In the meantime Confluence Cloud users with instances that fail with all Connect plugins should file a ticket.

[Robert Massaioli]

Hi David,

In the spirit of being an open company: the message is correct. We are updating our cloud infrastructure and it should make customers experiences even better. From our analytics we can see that this issue only seems to be affecting a very small number of customers for a very small number of add-ons.

Even so, we are treating this issue as a top priority bug and are working hard to get a fix out the door. Even so, because it is of both the nature of the fix and the low number of affected customers, we will be rolling the fix out to production slowly over the coming working days.

Cheers,

Robert

Note: This is only the case for Confluence. JIRA will likely stop showing this message sometime in the next week or two. There is less urgency there because an even smaller number of JIRA customers are affected by this issue.

[David Boyd]

Hi David,

The issue has been successfully resolved for Confluence and no Confluence customers should be seeing that message any more.
We are continuing to work towards resolving the issue for JIRA with urgency. 

Regards,

David Boyd

Atlassian Connect

[Oliver Buchmann]

Any progess about this?

[James Hazelwood]

Hi Oliver,

Thanks for your continued interest. We're very close to resolving the JIRA issue now.

Regards,
James