It is the same if constructors with multiple constructormodules are send to a starbase with the automatic system and the module queue does not use up all the constructormodules. The constructor with the remaining modules keeps in orbit and you never hear about it. 

Any starbase that can be upgraded that has a constructor in orbit has a green up arrow next to it.

True, but on the immense map I'm playing I have already 53 starbases and victory conditions say I still have to get control of 62% of the galaxy to get that influence victory. So please forgive me if that reminds me of the hitchhikers guide to the galaxy where the earthlings could have filed a complaint against the plans for the building of that interstellar highway because the were at display at the  planning department in Alpha Centauri for fifty years.

I'm talking about issue number 2, Taslios, and the fix is not the management screen or some arrow on the galaxy map, but instead a "turn-alarm" when there is an unused constructor-module at a starbase. Just like the idle-ship alarm or the idle colony alarm. I would even accept if the remaining constructor would autoeject at the starbase and go into the idle ship queue.

It's really great to have a more automatic system, but like with all automated systems, it needs monitoring - and one aspect of that monitoring is, that the system gives an alarm if it reaches point where the setup programm can not longer decide what to do next. That is the case if a colony has built all selected improvement or when ship reaches it destination ... or when there remains a constructor-module at a starbase after building all select modules.

I would not disagree with this at all!  The thing is buggy now plain and simple.  And that in itself is certainly causing a lot of the angst.  It does not know what to do with 'Stationed Constructors'  whether they are a left over point from a single constructor establishing a base with the pragmatic perk of two modules for a new starbase, or, an actual ship at the base with extra module points.  And it seems that if there are any points 'stationed' at all it does not use them when an upgraded module becomes available nor does it order a new ship to do the upgrade.  It's a mess.

 As far as I can see, the only way it works effectively is if you use a single constructor module ship and do not have the pragmatic perk where you get two modules for each single constructor module.

This feature needs some serious rework for sure.  A couple things to consider when fixing this.

- First, it has to use all points stationed to upgrade as things become available.  There should never be unused points if an upgrade for an installed module is available.

- Second, they should add a starbase configuration option to define what to do with auto requested ships that dock, apply whatever upgrades it can, and then it should either auto eject or stay stationed based on your setting. I do see some constructors auto eject occasionally but have not figured out what causes that.

- Third, it has to be smart enough to know how many constructor points are inbound from auto request ships....not how many ships.  This needs to consider perks to calculate the inbound points.

- Fourth, and this would be an enhancement.... it would be nice to be able to select what modules are auto upgradeable at the star base level.  So I have base supporting a research planet and I want the labs to upgrade as high as possible, however, after throwing on an initial manufacturing and morale module I do not want those 2 modules to auto upgrade further.

Anyway, there is some enhancement opportunity but if it could just effectively use the stationed points, calculate the auto inbounds correctly to know if it still needs to request more ships, and auto eject ships that still have modules after the starbase screen closes we would be further ahead.