Tie breaker's instance of Autosys (primary and shadow were already active) had a misconfigured config file, RoleDesignator=1 was the option set on it.
When the tie breaker was restarted, this instance somehow did not identify that the Primary scheduler was fully active and instead started up as another primary.
Release : 11.3.6
Potential racing condition with the HAPollInterval logic.
Example, say HAPollInterval=60 on primary and shadow, but HAPollInterval=29 on TieBreaker.
Because the tiebreaker has <1/2 of Primary+shadow AND its RoleDesignator=1, during the check it performs for Primary's presence, a racing condition could potentially develop and cause the tie breaker not to recognize the primary properly.