Attaching our homebase as reference,
this takes usually 5-10 minutes to become operational.

Noted facts:

• Inputs made are usually causing no visible change on the gates in the first 3-5 minutes,
• after this you can flip the gates, but their change does not propagate (especially activators/delays have this problem)
• after round about 7-8 minutes it starts to partially wake up and some connections start propagating statuses (and then sometimes get stuck in the middle of a delay-chain, or operate in weird client/server updating issues, like a 1s pulse traveling through a delay chain, sometimes makes attached doors show multiple traveling pulses)
• after 10-15 minutes it starts working properly

However:
ALL inputs made in the partially broken state are processed and make you easily lock some logic, as you literally flip a lot of gates at the same time when it finally wakes up.
All visible glitches, like

• clocks that do not visibly pulse but turn a light permanent on (instead of blinking)
• dual signal waves running through a single signal delay chain

vanish in the moment the logic starts working again.
It does also not require any additional wake-up call to operate again.

Loading the sector, and doing nothing for 15 minutes will make it work like a charm on first input.
If someone else enters the sector the logic stays functional on the client, and the new client can instantly see it working, so assuming this is a *server side issue*, assuming while the server stitches the logic modules together.

Complexity of logic systems seems to heavily influence this.
some stations with 10.000 logic modules and all are only used for small door/light controls and usually do not exceed round about 5-10 gates wired together, load in 20 minutes,
2000 gates wired together also load in that time scale.

Example:

Is the gate list for our base, all systems are wired in one large structure.

I know Bench also has a huge station with a long loading time and a lot of gates.
So we should have enough sources to benchmark this, and find solutions.
(Possibly split up in subsystems along "activators" as they are synced by server and client and thus could make reliable interfaces if the "any-to-any" lookup on building the logic tables is the issue.)

(tested by Andy, reconfirmed by Lancake)