Duplicate Betrothal to marriage "event" doesn't trigger

[Sarsante]

Information​

I have verifed my game files (Steam only)​

Yes

I have disabled all mods​

Yes

I am running the latest game update​

Yes

Required​

Summary​

Betrothal to marriage "event" doesn't trigger

Description​

Some of bertrothals I've made don't trigger, by that I mean there's no notification to accept the marriage when they come to age, I don't get the notification on the top of the screen and the betrothal can't be made into marriage.

I even managed to invite to my court my daughter's husband to be and I still don't get the notification to marry them. So they still forever betrothed unless I break it and do it again, then they get married instantly.

Check my oldest daughter in the save file I added, that's the most recent time it happened. She's 18 and they're betrothed since they're very young.

Steps to reproduce​

Get several kids betrothed and eventually one of them won't trigger and they'll be betrothed forever until you break it up and do it again so it's not like previously when we used to get the notification but they couldnt get married for some reason like becoming eunuch, holy order, being out of diplo range and other reasons.

Game Version​

1.9.0.2

Platform​

Windows

Additional Information​

Affected Feature​

Save Game​

View attachment marriage.ck3

Other Attachments​

 

[Genocidalvirus]

Verified this happened multiple times in two of my multiplayer games with no mods, both with the player and with the courtiers. I think it has something to do with the wife to be getting stuck in a location.

 

[Genocidalvirus]

Adding link to bug reports, including this one of this issue for visibility.
Betrothal to marriage "event" doesn't trigger
Betrothals, even without new T&T DLC, stopped working properly after Lance update
Betrothed characters don't get married (maybe it's grand wedding issue)
Grand Wedding betrothal broken even though one of the betrothed is underage

 

[Polished knight]

Hello there! We've already confirmed this issue, but thank you for the report!