Italian Primavera clubs not updating after promotion to / relegation from Serie C

The above issue appears to still be in the full game. Surely it is not correct?

I uploaded a save into the cloud service (non-league_primavera.fm).

In the screenshots attached to this post, one can see how Virtus Verona were relegated from Serie C after 23/24,  and yet their U20s remained in Primavera for subsequent seasons without the main team playing in Serie A/B/C. So relegated clubs not removed from Primavera, and promoted clubs not added to Primavera.

Additionally it looks like after the first season Southern clubs are placed in group A, and northern clubs in group B in Primaveras 3 and 4. Should probably be the other way round.

I've moved this across to the Italian Competition section. It will allow the most appropriate part of the QA team to investigate and review further.

Correct, it should work that way but seems unfortunately not

Thank you for moving the post to the appropriate section.

Hopefully the team entries will be fixed at some point.

@Michael Sant Yes this is definitelly a bug. 

The U18 team is correctly handled (if a club is relegated from third division to fourth it will be removed - and a club promoted from fourth to third is added).

The U20 is not handled at all.

Please solve this issue.

Edited November 26, 2023 by axel.pezzo

After discussions with the research team we have highlighted issues as has been mentioned and we have these under review. Thanks for providing this information.

Il 28/11/2023 in 21:19 , Michael Sant ha scritto:

After discussions with the research team we have highlighted issues as has been mentioned and we have these under review. Thanks for providing this information.

I saw that the fix is not in the 24.2 patch, isn't it? There is a date in order to be released?

We wouldn't be able to put a specific date on when this would be resolved. It is still under review with our team at present.

I have been postponing an Italian save because of this, so hopefully this is being looked at and a fix is released soon.

This has now been resolved via a previous update, thank you for your patience.