Cruel act 2 Ascent to power quest and uninterractable ascendancy shrine

Dunno if you are still having an issue with this, but I got stuck with the search traitors passage as well, but it happens that you don't have to get said quest item again, beat the boss then go to nearest waypoint, click on the passage and you should see trails waypoint already unlocked. Hope it helps some of you!

So apparently this is still bugged.
Finished the trials 2 times now and I'm unable to interact with the ascendency shrine.
Please tell me I don't have to run a third time.

Hey guys I might have fix the issue
The quest that make you go to harder levels for me was not completed so I had to go back to talk to the two npcs then teleport for act 1-3 normal is gone going through act one hard now to see if it’s completely fix

Edit: nope but still hoping it’s one of those thing where I have to find the location after doing some more quest of act 2

same issue

+1

I think it might have happened for me when I picked up a djinn barya from a2 normal in my stash while in a2 cruel town, before I fought balbala again. I got the quest and then it wouldn't progress once I killed her and got the a2 cruel barya.

GL devs on finding the fix, loving the game!

J'ai le même problème explorer le passage du traître aidez nous merci

I am also having the same issue in cruel difficulty, killed the boss, no quest item found so the quest did not continue. I tried to just waypoint to the trial and did it using my lvl 51 thing but it wouldn't let me get my ascension points after completion. Hope y'all fix it soon, I fear I'm going to mess something up further if I keep playing so I will stop until it gets fixed. Have loved the game so far and have been playing nonstop since release but this is disappointing.

I just realized i had this quest and I've cleared the Traitor's Passage and defeated the djinn twice and went to ascend at the Trial of Sekhamas ... is there any solution or am is it bugged?

same, 75 pages of this bug, please help !

great game though

Ah, seems there's 2 threads about this bug. Yep, having this issue too.