Error stating there is no room for baby when opening the game

Product: The Sims 4
Platform:PC
Which language are you playing the game in? English
How often does the bug occur? Often (50% - 99%)
What is your current game version number? Version 1.103.315.1020
What expansions, game packs, and stuff packs do you have installed? All expansions, game packs and stuff packs. Only missing the following kits: Bust the Dust, Throwback Fit, Fashion Street, Incheon Arrivals, Carnaval Streetwear, Simtimate Collection, & Poolside Splash kit.
Steps: How can we find the bug ourselves? End a game with a baby in a bassinet in the household (i.e. exit the game before it ages up); close the EA app and then open it up again.
What happens when the bug occurs? When I open up a save with a baby already in the household, I get a pop-up that states that there is too much clutter in the house for the baby to fit and that it was put in the households inventory. It's happened now on 3 separate save files with 3 different families.
What do you expect to see? I expect to open my game and the baby's bassinet is exactly where it was when I closed the game.
Have you installed any customization with the game, e.g. Custom Content or Mods? Not now. I've removed them.
Did this issue appear after a specific patch or change you made to your system? Yes
Please describe the patch or change you made. This started after installing For Rent.

‌

This glitch started happening after I installed and started playing The Sims 4: For Rent.  The family I was playing would have a baby on the lot when I'd save and close the game. When I would got back into the game, I would get a pop-up telling me that there was too much clutter in the household and the baby couldn't fit and that it had been moved into the household's inventory. This glitch would occur approximately 80 to 90% of the time if I exited the game while a baby was in the household I'd been playing. Initially, I had some mods in my game; I took them out and this glitch still occurs. I've tried starting a new save file - thinking that, perhaps, that save had become corrupted; still happened. I experimented with some older saves that I strictly use for building and it still occurred.