Seeing error as "Draft versioning is not supported. Conflict 409
Asked by Biju Somarajan:

The Conflict I see while publishing is as follows - How to resolve this

{statusCode: 409,...}  
data: {authorized: false, valid: true, allowedInReadOnlyMode: true, errors: \[\], successful: false}  
allowedInReadOnlyMode: true  
authorized: false  
errors: \[\]  
successful: false  
valid: true  
message: "Draft versioning is not supported. Current version is : 21"  
reason: "Conflict"  
statusCode: 409


Answers:
author: roman
body: Hi [@Biju Somarajan](/t5/user/viewprofilepage/user-id/1461419),

do you refer to publishing with Scroll Versions? If not, please share where in Confluence do you see this error, or which app do you use to reproduce it?

Roman.

comments: author: Biju Somarajan
body: Basically a user was trying to publish a drawing (Gliffy) in Confluence and he took a while to finish the drawing and we do keep on saving while he was progressing and use to do open the draft page from different labtops and do update some and when he finished the drawing he was trying to publish it will wait on the page for some time and will show and error message failed to publish - The error on UI is " Can't Sync with the server" - Refresh the Page to try to re-establish the conection", from developers tool on browser we could see the following logs.

{statusCode: 409,...}  
data: {authorized: false, valid: true, allowedInReadOnlyMode: true, errors: \[\], successful: false}  
allowedInReadOnlyMode: true  
authorized: false  
errors: \[\]  
successful: false  
valid: true  
message: "Draft versioning is not supported. Current version is : 21"  
reason: "Conflict"  
statusCode: 409

Work Around we tried is : Down load the Gliffy diagram and create a new page and publish.


author: roman
body: [@Biju Somarajan](/t5/user/viewprofilepage/user-id/1461419),

409 code is a conflict error, but it might be hard to understand why it happened. At least without the logs from the same time period.

I assume you are using Confluence with collaborative mode enabled. If you are not on the latest release of Confluence there is a good chance that such issue is resolved there as Atlassian is continuously improve synchrony.

We at K15t encountered 409 error with one of our apps. We couldn't find the route cause of the issue, but had a suspicion that it was related to a large number of DB requests to a synchrony server within a short time-frame.

Do I understand correctly that the workaround helped, and you were able to save the page with the Gliffy macro?

Roman.


author: Biju Somarajan
body: I can provide logs let me know how to get that to you.

We have collaborative mode enabled but the issue we see is on single user instance not on team pages and mainly where Gliffy diagrams is involved.

Yes work around helps like saving glify and add the same to a new page and publish it.


author: Biju Somarajan
body: Entire team is affecting now and it is nightmare , I ma planning to open a help desk ticket for this


author: roman
body: [@Biju Somarajan](/t5/user/viewprofilepage/user-id/1461419),

if your Confluence user license includes access to Atlassian Support, I would recommend to do that.

I would also contact Gliffy to see if they have anything to suggest as the issue seems to be happening on pages with Gliffy macros only.

Hope this helps.

Roman.


Tags: confluence-server

server