# Org unit closed date not enforced for event data entry

**URL:** <https://community.dhis2.org/t/org-unit-closed-date-not-enforced-for-event-data-entry/74572>\
**Category:** Support - Assistance technique\
**Tags:** tracker\
**Created:** [16 June 2026 15:46 UTC](https://community.dhis2.org/t/org-unit-closed-date-not-enforced-for-event-data-entry/74572 "2026-06-16T15:46:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![didate](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/didate/32/29381_2.png) [@didate](https://community.dhis2.org/u/didate)\
**Post date:** [16 June 2026 15:46 UTC](https://community.dhis2.org/t/org-unit-closed-date-not-enforced-for-event-data-entry/74572/1 "2026-06-16T15:46:41Z")

</div>

Hello everyone,

I have an org unit (`__PS Saourou`, level 6) with a **closed date set to 30 September 2025**. However, in the Capture app I was able to register and complete an **event dated 13 June 2026** — well after the closed date — without any validation error or warning.

For aggregate data entry, the opening/closed dates are enforced and block periods outside the active window. But for event/tracker programs, it seems the closed date is simply ignored for the event date.

My questions:

1. Is this the expected/intended behavior ?
2. If so, what is the recommended way to **prevent event registration after a given date** for a specific org unit?
3. Is there any plan/Jira issue to align this behavior with aggregate data entry?

I’m on DHIS 2.41.

Evidences :

 ![image](https://dhis2.b-cdn.net/uploads/default/original/3X/9/f/9f15b93482c2806a0d255acfb6c301af4cf1029f.png)

 ![image](https://dhis2.b-cdn.net/uploads/default/original/3X/4/a/4a5c1b20b27badc7782792d1fbd0330a327028f3.jpeg)

Best Regards

---

<div class="post-metadata">

**Author:** ![Gassim](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/gassim/32/35347_2.png) [@Gassim](https://community.dhis2.org/u/Gassim)\
**Post date:** [24 June 2026 09:02 UTC](https://community.dhis2.org/t/org-unit-closed-date-not-enforced-for-event-data-entry/74572/2 "2026-06-24T09:02:20Z")

</div>

Hi @didate

Thank you for raising this issue. It appears to be a known bug issue: [Opening and closing date not being taken into account in Capture app - DHIS2-17544](https://dhis2.atlassian.net/browse/DHIS2-17544). I will raise this again to the team. 🙏

---

<div class="post-metadata">

**Author:** ![didate](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/didate/32/29381_2.png) [@didate](https://community.dhis2.org/u/didate)\
**Post date:** [24 June 2026 15:04 UTC](https://community.dhis2.org/t/org-unit-closed-date-not-enforced-for-event-data-entry/74572/3 "2026-06-24T15:04:28Z")

</div>

Hello @Gassim ,

Thank you for raising it again in jira. Hope it is going to be fixed soon.

Have a good one.