When I have a bloq with a relationship field with a minimum number of related entries, the validation on that fields can sometimes put the entry into an unsaveable state. The most straightforward test is to create a single bloq with a single relationship field with a “minimum number of related entries” configured (attached image).
Then on the entry, add a couple related entries to this field. We can see that anything less than 2 triggers the async validation, which seems to work so far (attached image).
Now, add a third entry here so the on-page validation passes, and then quickly delete one and click Save before the async validation marks this field as invalid again. The easiest way to do this might be to make your browser window short so the Delete icon is right under the Save button so you can click them quickly (attached image). If you triggered it correctly, then on page load you’ll have the standard EE error about the entry not saving correctly (attached image).
Finally, add another entry to this relationship field and the on-page validation should trigger, but the error text in the relationship block will persist and the Save button remains disabled (attached image).