If you turn yours on/off repeatedly, you might see the swapped behavior at some point.
If so - then it means that instead of some straightforward, deterministic method such that it's always one, then the other (a common feature of 3rd generation software design on older architectures and operating systems), but is instead stochastic, meaning that you can't predict it (because the two discrete commands are given over to a scheduler that NEARLY always does what you expect in ordering the commands - a common behavior of modern systems) - then it's beyond the control of the programmers, without changing things that should never be changed, such as the various layers of the multitasking core.
That - or they have to do a re-write to straighten out whatever assumption was made in the "light up" routine.
In the case of trying to find time or resource to rewrite the light-up sequence, when ultimately both are working after a brief pause, in light of all the other work to be done, software engineers and programmers and their management have argued - successfully - for years:
It's not a bug.
It's a feature.
PS - Based on past similar experiences - this issue was latent and has come to light now that everything's running quicker / different. Very common deal.