Duplicate Stellaris - Sector auto-add systems we just remove from them

[Hogloo]

Description
Sector auto-add systems we just remove from them

Game Version
Gemini 3.8.2

What version do you use?
Steam

What expansions do you have installed?
Synthetic Dawn, Utopia, Leviathans Story Pack, Apocalypse, Megacorp, Distant Stars, Ancient Relics, Lithoids, Federations, Nemesis, Aquatics

Do you have mods enabled?
No

Please explain your issue is in as much detail as possible.
When I remove a system from my sector, it comes back inside the next second. You can see it in the images I named 1, 2 and 3 which describe the chronological order: it's not even a monthly sector update but instantaneous.

It really bothers me because I plan to release this sector as a vassal but I don't want to give it the rare material deposits of this system and another...

Steps to reproduce the issue.
Try to release one system from your sector, without adding it to an other sector.

Upload Attachment
File(s) attached

 

[Cast Iron Duck]

I'm having this exact problem. In a game last week it worked fine, and for some reason I'm having this same problem in today's game. It's like a system yoyo.

ETA: I'm using the sector editor to remove systems from a sector. I remove them, and they return a second later.

Editing again to add: I first ran into this when trying to sectorize and vassalize an FE. I deleted that sector and tried creating some new ones. Same problem: if you delete a system from a sector, it reappears a second later.

 

[Crystal Nole]

Can concur I've had this problem when trying to remove sectors, it just readds the removed system right again afterwards.

 

[Cast Iron Duck]

I have a suggested work-around if you're planning to vassalize the sector. If the game is paused, it can't revert the systems. Add or delete anything you want while the game is paused, then, without unpausing, create a vassal of the sector. It will stay the way you set it.

 

[Meme_Drone [Qloc]]

Hello!

Thank you for the report!

We are aware of the issue, it has already been added to our bug database.