409 conflict creating block

Jonas Widenberg

Vote:

Hi! I'm having an issue creating a certain block of mine. It occurs both in production and in development and also running version 10 and the latest version.

When creating the block I get an error in my browser console stating a 409 conflict error. It happens approx 80 % of the times trying to create the block.

Request URL: http://mydomain/EPiServer/cms/Stores/contentdata/
Request Method: POST
Status Code: 409 Conflict

The request payload:

{
  "name": "New Blockaaaa",
  "parentLink": "5_76891",
  "contentTypeId": 46,
  "properties": {
    "icategorizable_category": [],
    "image": "/link/8690b853be154572967feb02028fef05.aspx",
    "name": "xx",
    "title": "xxxxx",
    "mainBody": "asdfasfd",
    "phone": "xxx",
    "email": "xxxxx"
  },
  "createAsLocalAsset": true,
  "autoPublish": true
}

I can't see anything strange with the block other than that it inherits from another blocktype. But thats alright isn't it?

#186330

Dec 18, 2017 9:11

Hovard Berg

Vote:

+1. We are experiencing the same issue.

#186675

Jan 02, 2018 10:59

Jakob Jaber

Vote:

Did you solve it? I am experiencing the same issue.

#191036

Apr 19, 2018 12:02

Vote:

Can you post the code?

#191092

Apr 19, 2018 23:18

Trung Pham

Vote:

Please review this knowledge base and let me know if it helps

https://support.episerver.com/hc/en-us/articles/360002910312-409-conflict-Creating-page-block

#191098

Apr 20, 2018 5:49

Raffaele Millo

Vote:

I am experiencing the same issue. (Version 10)

I have reviewed the solution suggested in the link above https://support.episerver.com/hc/en-us/articles/360002910312-409-conflict-Creating-page-block and can confirm this occurs even when with existingResponse attribute is set to

existingResponse="PassThrough" />

or it's not added.

Here are some more details:

issue seems to occur for certain blocks only
- blocks have required properties and non-required properties
- most properties are culturespecific
issue occurs only when user tries to create these blocks from ContentArea
- issue never occurs when blocks are created on the Assets panel
- Response is
  - message: "Unable to load /secui/cms/Stores/contentdata/ status: 409"
  - url:"/secui/cms/Stores/contentdata/"
  - responseText: "The page was not displayed because there was a conflict."
  - status:409
  - statusText:"Conflict"

#192624

May 21, 2018 18:29

Magnus.Ellinge

Vote:

We had a selection factory which timed out causing a 409. We checked the logging and got an Unexpected error when requesting model accessor which pointed us to the problem in the stack trace.

I would check the logs for MetadataStore for any hints of what goes wrong.

In our case:

Unexpected error when requesting model accessor for EPiServer.Core.ContentData with parameter {"parentLink":"117","contentTypeId":24} System.Net.WebException: The operation has timed out at Sys (..)

EPiServer.Shell.UI.Rest.MetadataStore

ERROR

#194553

Edited, Jun 25, 2018 13:28

Vote:

If you are using a version earlier than 11.8 this can be caused by a custom validator which fires a validation message, but is not displayed due to bug Bug - CMS-11522

Read more on https://world.episerver.com/support/Bug-list/bug/CMS-11522

#198498

Oct 30, 2018 5:25

Brian

Vote:

I have recently started to see this error message and am on EPiServer.CMS.UI 11.16.0.

#206214

Aug 07, 2019 13:23

Tomas Hensrud Gulla

Vote:

We are seeing it on EPiServer.CMS.UI 11.18.0. It only happens when creating a block with custom validator from the ContentArea. When creating from assets pane, it works.

Same issue as described here: https://world.episerver.com/support/Bug-list/bug/CMS-11522

#209034

Edited, Nov 06, 2019 13:17

Try our conversational search powered by Generative AI!

409 conflict creating block