Plugin not working - problem retrieving the macro

[Andrew Beak]

I'm trying to use the OpenAPI swagger plugin (marketplace)

When I insert it onto a Confluence page it displays an error that says "Problem retrieving the macro".

If I look at the Javascript console I can see some errors, including a 404 to 

https://example.atlassian.net/wiki/rest/api/content/7733249/history/1/macro/id/8524fc4a-a246-4b49-a3d9-17aa2d4d24ed?_r=1559300452834

The response in this file is:

{"statusCode":404,"data":{"authorized":false,"valid":true,"errors":[],"successful":false},"message":"com.atlassian.confluence.api.service.exceptions.NotFoundException: No macro found on content id : ContentId{id=7733249} with version: 1 and macroId: 8524fc4a-a246-4b49-a3d9-17aa2d4d24ed"}

Is this a problem with Confluence?  Or is it something specific to this plugin?

[Alex Medved _ConfiForms_ · Accepted solution]

I believe you are using the new editor for Confluence, right?

Seems to be related to

• https://jira.atlassian.com/browse/CONFCLOUD-65717
• https://jira.atlassian.com/browse/CONFCLOUD-64923

Don't get tricked that it says resolved for the 2nd ticket, it is clearly not... we, as authors of couple of apps for the Confluence cloud are affected quite a bit by this

The problem is that the macro configuration is not persisted to the storage and therefore cannot be retrieved (immediately). If you wait a bit in the editor,... or save the page and then re-open in edit mode, then you will see the macro config get's found

[Andrew Beak]

Hi,

Thanks for the reply, that's extremely helpful.

Yes we're using the new editor.  The 404 I'm seeing definitely sounds like a good fit for that second ticket you linked.

I tried waiting on the page as well as save/reopen but neither of these workarounds have made a difference.

Do you know if there is a way to use the old editor?  I don't spot anything in the Confluence settings that let me choose.

[Alex Medved _ConfiForms_]

People are asking about it here, https://community.atlassian.com/t5/Confluence-discussions/Try-out-the-new-editing-experience/m-p/1000813

but I have not noticed any official answer from Atlassian... some mentioned that it is possible to ask Atlassian support to get old editor back.

In our instances we have quite a different experience - in one instance we can create pages in new editor, but have an option to choose old editor, whole in another instance the old editor is still the default and we are offered to create new pages with "new editing experience"

Feels very inconsistent and.. well.. broken

[Alex Medved _ConfiForms_]

Actually, the first linked issue is also relevant - see the last comment from Scott