The logic is twofold:

1. It first checks to ensure that you have enough active players at each position matrix grouping - in the case of QB, only QB can be there, so it's going to make sure you have 2 active QB's. If it can't fix this by activating players on your roster then it will sign and release players.
2. It then checks to make sure you have enough active players at each depth chart position. If #1 passes, #2 should have enough players to do no more than modify your depth chart with players that are already active.

The 'probably' language was because as hard as it's been to coordinate all these changes I'm still watching to ensure that everything is happening as expected.  😁

Well, doesn't say throwing hand...

Was the probable or worse than that?

Appreciate the caution.

With regards to state that of mfn-test, can't speak for anyone else but happy enough with SIM changes. Depth chart needs at least another season, we need to get through at least half a sedon with no issues imo. Problem then is, we know how it works so can avoid the problem - I **** apparently, so will try to force issues next season.

Perhaps I missed it somewhere, but when considering roster minimums, are teams supposed to continue to follow the minimum requirements for each position found under the roster distribution tab?

I need to figure out what to do with that. It actually may be no longer needed now that we have the warning banner and something we're enforcing.

What, if anything, can be done about the auto manager's roster decision making? The worst being when it cuts starters or high rated players. Then, next worst is when it does not re-sign a player that was a first, second, or third round pick or a "boomer" whose initial contract is up and needs renewal. There should be a minimal default value or formula for re-signing/contracting those players. Instead of letting a good starting player go, and replacing with an old veteran, lacking speed, with a full salary/bonus for 6 years? Especially the players who were high draft picks and have finished their 4 year initial contracts.

Still, I don't understand your complaints.
Maybe I'm just lucky and have fewer injuries; maybe that's exactly because of my fatigue setting.
In any case, it works for me when I manually clear the warning about gaps in the lineup. There haven't been—and still aren't—any unintended automatic cuts or new signings on my team.
I double-checked my comment from back then (Week 4) and concluded that I had initiated the cuts and signings myself and that there was no intervention by the AI.

So the criticism here is confusing me more and more.

Ioan. What I was referring to are unexpected auto-mgr cuts, in my own case, was the release of my starting CB1 when he was Q injured and deactivated. There was no warning banner regarding a roster issue. I believe that problem has been fixed, but not sure. Hopefully so. The release error by the auto mgr ... 2077 2077 Game Week 11 #24 Zachery Obrien Released by Denver

he was then signed right away off waivers, my waiver claim was not on the league transaction record, another anomally......

2077 Game Week 12 #24 Zachery Obrien Signed contract with Tennessee ($7,171, 1 yrs)

I let JDB know about it right when it happened, I didnt get a reply on that one, which is OK, and Ray/Titans was graciously willing to let Obrien go or trade him back, he can verify that I said go ahead and keep him, the Test League is primarily for finding problems. Hope that clears up what my particular complaint was about the A Mgr.

As far as fatigue settings, I use custom and set them low for all positions other than QB and Kickers. You can tell from my player stats.

Then, the seperate issue is the A Mgr's managing in general, which is what ruins A Mgd teams. My preference would be that the A Mgr would not wreck a teams roster, like they have to date. Is there any doubt about that?

Now I got it.
I was only confused, as this AI intervention never happened with my roster even with Q injured players.

I agree that the AI management needs work - but that's outside the scope of this update.

For the CB that was cut, I'm pretty sure that was when we were still having issues with the auto-depth chart manager being too aggressive. I believe that has been settled but I want to see an offseason and start of season to fully validate.