 Maximum Instance Age bug

I noticed that, setting a different `mia` than default value during Container creation, the expiration time of children content instances doesn't change but still remain equals to 2 years.
Can you explain me how to correctly set up this feature?