Ah, good to know. Still a bug, but at least if there's a workaround. Still completely unacceptable that at the very least there is not an accurate error message. That is just some cut n' paste coding right there. It's a real waste of time for those effected and no reasonable way to make it up as the event just runs for 24 hours a month. Waiting days for a response is just not acceptable either.
To be clear, I am not 100% confident this is the answer. All I know is that it is a bug and prevented me from making any progress beyond the initial unlock. If it is the answer, then what is being done to verify and resolve this? It impacts gameplay moving forward because of the scarcity of the event. Since this is not a verified solution, I can't just wait until next month to see if the theoretical fix works. If the same thing happens again then I have wasted two months on this event. So we still need an RCA from support/dev and a resolution (verified workaround or code fix).
This happened to me today for the Executor event. Is the bug being fixed?
