New pages result in warnings 'Unable to POST item: translation.macros'

[Arno Wetzels]

Since last week users receive 3 warning messages in the top right corner of the screen upon creating new pages in Confluence Cloud. After creation, also updates on those pages result in the warnings.

Existing pages seem not to show this behavior.

Any ideas where to find the cause of this seemingly harmless but annoying issue?

The three warnings are always the same:

'Unable to POST item: translation.macros.number'

'Unable to POST item: translation.has.macros'

'Unable to POST item: translation.macros'

Each warning is followed by 'There was a problem communicating with the server. Please refresh the page and try again'.

[Marc - Devoteam · Accepted solution]

Hi @Arno Wetzels 

Welcome to the community.

This seem to be an issue, that might relate to your Confluence instance.

My advise is to reach out the Atlassian Support to address this issue.

[Arno Wetzels]

OK, thanks for the quick reply. I raised a ticket with Support so let's see....

[Arno Wetzels]

Reply from Atlassian Support: "Looks like the error is due to an update available for App Translations for Confluence on your instance, could you please try after updating the app and let us know if you are still facing this issue."

For us this solved the issue.

[Lutz Hoffmann · Accepted solution]

Exactly the same problem in my instance... :(

[Nicholas Straw]

We have the same issue since last week. 

[Arno Wetzels]

Reply from Atlassian Support: "Looks like the error is due to an update available for App Translations for Confluence on your instance, could you please try after updating the app and let us know if you are still facing this issue."

For us this solved the issue.

[Lutz Hoffmann]

As far as I know we do not use that app

[Lutz Hoffmann]

Problem was solved by updating the mentioned app.

[Dmitrijs]

Hi,
The same problem regularly appears. Have had this app., however, we refused from it. So actually there is nothing to update (at least based on my understanding). So far no any idea, how to clean it up,

thanks

[Ferdinand Mul]

The same over here, referring to te page I was working on at that time:  from September 8 and on. We are using Atlassian cloud services, not a setup on precinct.

At first I thought it was page specific, I see it happen now more often so this becomes a page independent, and space independent, issue for me.

A critical note. Not even sure if we use this app, is the app mandatory for having the issues?