Issue of Inconsistent Event Expiry Behavior in DHIS2

I am facing an issue in DHIS2 when configuring the Completed events expiry days and Expiry days settings. The goal is to allow the modification of events from the previous month until the 4th day of the current month, after which all events are locked to prevent further edits.

Here are the settings I used:

Completed events expiry days: 5

Expiry period type: Monthly

Expiry days: 6

The settings generally worked as expected, with events being locked at the right time. However, I encountered an inconsistency in event behavior:

Some events from the same month were locked (expired), while others remained open and editable.

Example: Two events entered on October 12th — one was locked (expired) and the other remained open for editing, even though both events are within the same period.

Question:

What could be the possible reason for this inconsistency in event behavior? Could it be related to the completion date or other settings affecting event locking? How can I ensure that the settings are applied uniformly to all events within the same month?

Hi @Nour_Albakeer

Thank you for the post. May I ask if this is happening for the same user?

Any other similarities/differences between these events that you could gather?

Thanks!

Hi @Gassim
Thank you very much for the response.
Yes, it is happening for the same user. The events occurred on the same date and are of the same type.
Additionally, the settings applied affected the editing of events that took place within the same month.

Could you please assist me in setting the required configuration to prevent users from editing data from the previous month until the 4th of the current month without causing any issues?