[NOT_REPRODUCIBLE] The "field is required" validation is incorrectly triggered in Draft versions

I have…

  • Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • Regression (a behavior that stopped working in a new release)
  • Bug report
  • Performance issue
  • Documentation issue or request

Current behavior

The “field is required” validation is being applied when it should not be.

Steps to recreate:

  1. Set the field validation to Required when publishing.
  2. Fill in the content for this field and save.
  3. Remove the content from this field and save.

You receive the validation error “field is required,” even though it should not appear, as the version is still in Draft.

Expected behavior

No validation is applied

Minimal reproduction of the problem


  • Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • Cloud version

Version: [VERSION]


  • Chrome (desktop)
  • Chrome (Android)
  • Chrome (iOS)
  • Firefox
  • Safari (desktop)
  • Safari (iOS)
  • IE
  • Edge


Good catch. I will have a look.

1 Like

Now I am confused. Are you talking about

“Required when publishing”?

The first one is always checking for fields. The second only when the content is either published or moved to publish status.

Required on publishing.
I noticed that this error no longer appears in the cloud. Has it been fixed?

Not recently. I can also not reproduce it, therefore I am a little bit confused.