When there are multiple bloqs fieldtypes in the same channel, after adding enough elements in some of them (this number seems to depend on other factors) the entry gets blocked by a date validation error saying the publication date field is empty while being mandatory. This is wrong as the field is visibly holding it’s usual value. The error blocks any subsequent update of the entry and in addition it affects the entry status field in the “Options” tabs removing the selected choice (none of the radio buttons there looks selected even though it is). On page refresh everything looks fine but any attempt to re-save the entry results in the error popping up.
Manually deleting some of the created bloqs elements for that entry from “blocks_block” in the database seems to “free up” some space, unlocking it for changes. In some cases this even allows the addition of more elements than the amount of the removed ones but eventually the entry locks up again. This cycle can be repeated to gradually get more content in but obviously this isn’t a solution.
It also seems that having bloqs fieldtype with bigger selection of types are triggering the issue earlier - fewer complex fields with less data seem to cause the error earlier than more, simpler fields with more data. For example in the attached images 60+ elements were needed to trigger the error but in entries with more complex fields 18-20 elements were enough.
In some cases different notices and warning pop up - these can be seen in the attached images. In that particular case the elements that are seen at the bottom were actually children of 2 other levels before them - these parents disappeared, the children moved to root level on that field and all these notices displayed before them.