[Repro needed] The Oracle daily test conversation window auto close issue

Title: The Oracle daily test conversation window auto close issue
Reproduction Rate: 5%
Blocker?
Details: The Oracle daily test
click on test keyword and he will ask you to answer yes or no
sometimes conversation window auto close itself after click on test keyword in 5 seconds so i can not answer yes or no
and you can not get reward this time
if you ask test again he will say too soon to test
----------------------------------------
So can we just change some way to avoid this issue
like if you did not answer yes or no,than you can test again to get daily reward
----------------------------------------

 

@Fox Blue
I was not able to repro this. I waited a good while before answering and the conversation did not auto close in the meantime...
Do you have anything in your interface customized perhaps? Conversation closed ups disabled, etc? This may be an important part of the repro.
I recommend trying it again in the next QA build. If it still happens please report back, and please use /devbug so we can see what build you are on. Thank you!

 

@Lexie it happened long time before R53,R53,even happened R54QA

case 1. Reproduction Rate: 5% hard to find out what conditions
[Enable Conversation closed ups] [in multiplayer Open mode][login in The Oracle]
[There is a player next to me,and he talk to The Oracle,maybe]
The Oracle daily test
click on test keyword and he will ask you to answer yes or no
a small chance conversation window auto close itself after click on test keyword in 5 seconds so i can not answer yes or no

case 2. Reproduction Rate: 100%
[Enable Conversation closed ups] or [Conversation closed ups disabled]
The Oracle daily test
click on test keyword and he will ask you to answer yes or no
conversation window auto close itself after click on test keyword in 70-90 seconds if i did not do anything ,by design
so if i just do other thing[google translate中文 the test] can not answer yes or no,when the timeout,it close

---------------------------------------------
this is why i have a suggestion to avoid this issue

Add verification to determine if the daily test was completed correctly
---------------------------------------------
if my luck case 1. it happens again,i will use /devbug in the next QA build to help