Why is an active hierarchy version that has been saved recently sometimes set automatically to inactive?

The newly edited hierarchy is saved as an auto-commit process, even before you save and close it. The application triggers the tree flattening service and the audit job, when you save and close your changes. It doesn't wait for the job to complete, and notifies you to revisit the version after the audit job is complete, to check the version status of the hierarchy.

If the audit job identifies any errors at the time of hierarchy validation, then the status of the hierarchy is set to Inactive. However, the application doesn't notify you of this. You must revisit the hierarchy management interface and rectify issues in the previously saved version, if the status is inactive.