Phoenix Upgrade 10.1.0: UI Issues and Bug Inquiry

Ben M. · 2025-05-30T15:20:51.230Z

We recently upgraded form phoenix 9.4.0 to 10.1.0 and are experiencing some oddities in the UI now. 1. New traces are not streaming into the project view. This seems to be triggered by opening a trace, but the only fix we’ve found is to refresh phoenix (or change our timeframe). This makes it hard to monitor over time 2. I can’t close a trace view by clicking on the background page any longer. It now opens the traces that I click on, despite not being able to see what the trace details Are these known behaviors (and considered to be bugs?)?

12 comments

· Sorted by Oldest

Ben M.
·
This is where I used to click to close my traces view
RunLLM
APP
·
1. The issue where new traces do not stream into the project view after opening a trace, requiring a refresh or timeframe change, is a known bug. There are reports of the trace table query not refreshing while the page header query does, and similar UI regressions have been noted in recent versions (trace table query does not refresh, tracing slideover regressions). 2. The inability to close a trace view by clicking the background, and instead opening other traces, is also a reported UI regression. This behavior is documented as a bug in the playground's slideover interaction (tracing slideover regressions). Would you like more detail on workarounds or tracking these issues?Sources: - trace table query does not refresh - tracing slideover regressions
💡 Hint: Mention RunLLM in the thread for followups.
Ben M.
·
I’m not sure that those are the same issues that I’m referring to. The slideover regressions might be related, but the refresh but was back in April
Anthony P.
·
1.
Does trace streaming resume when you close the slideover? It is intentional behavior that streaming stops while a trace is being viewed
2.
This is a regression, apologies
Ben M.
·
No, closing the slideover does not resume streaming. I can see GQL requests flowing in my browser network console but nothing shows in the UI. It’s like they get black holed.
Anthony P.
·
Hmm, okay, that is not intentional. Is this just on the traces tab, spans tab, or both?
Ben M.
·
I’ve only been using the spans tab, but of course now that I reference it and am looking, it resumed correctly 🤔 I’ll see if I can repro in the next few minutes. I did notice 3 requests fail because of an expired JWT. I wonder if that expires while the slideover is open it causes the JWT never to renew until refresh
Anthony P.
·
that's an interesting observation. Any gql refresh that fails due to auth should be retried automatically with a refreshed token. Perhaps something prevents that for the polled trace requests
Ben M.
·
Maybe. I can’t repro in our deployed environment at the moment, so it seems like it could be intermittent. I know it’s something that has happened at least once because another teammate (Vicky B.) mentioned it at our standup this morning 🙂 If I can get it to happen again, I will submit an issue on the repo with all details I can capture and I’ll ping you in this thread. Not much you can investigate without more info, after all
Anthony P.
·
I don't mind an early issue if it's difficult to repro, at least we can have something tracked! I can file an issue on the slideover backdrop and link here 🙏
🙌1
Ben M.
·
You’re the best! Thanks
Anthony P.
·
https://github.com/Arize-ai/phoenix/issues/7814

Ben M.
·
This is where I used to click to close my traces view
RunLLM
APP
·
1. The issue where new traces do not stream into the project view after opening a trace, requiring a refresh or timeframe change, is a known bug. There are reports of the trace table query not refreshing while the page header query does, and similar UI regressions have been noted in recent versions (trace table query does not refresh, tracing slideover regressions). 2. The inability to close a trace view by clicking the background, and instead opening other traces, is also a reported UI regression. This behavior is documented as a bug in the playground's slideover interaction (tracing slideover regressions). Would you like more detail on workarounds or tracking these issues?Sources: - trace table query does not refresh - tracing slideover regressions
💡 Hint: Mention RunLLM in the thread for followups.
Ben M.
·
I’m not sure that those are the same issues that I’m referring to. The slideover regressions might be related, but the refresh but was back in April
Anthony P.
·
1.
Does trace streaming resume when you close the slideover? It is intentional behavior that streaming stops while a trace is being viewed
2.
This is a regression, apologies
Ben M.
·
No, closing the slideover does not resume streaming. I can see GQL requests flowing in my browser network console but nothing shows in the UI. It’s like they get black holed.
Anthony P.
·
Hmm, okay, that is not intentional. Is this just on the traces tab, spans tab, or both?
Ben M.
·
I’ve only been using the spans tab, but of course now that I reference it and am looking, it resumed correctly 🤔 I’ll see if I can repro in the next few minutes. I did notice 3 requests fail because of an expired JWT. I wonder if that expires while the slideover is open it causes the JWT never to renew until refresh
Anthony P.
·
that's an interesting observation. Any gql refresh that fails due to auth should be retried automatically with a refreshed token. Perhaps something prevents that for the polled trace requests
Ben M.
·
Maybe. I can’t repro in our deployed environment at the moment, so it seems like it could be intermittent. I know it’s something that has happened at least once because another teammate (Vicky B.) mentioned it at our standup this morning 🙂 If I can get it to happen again, I will submit an issue on the repo with all details I can capture and I’ll ping you in this thread. Not much you can investigate without more info, after all
Anthony P.
·
I don't mind an early issue if it's difficult to repro, at least we can have something tracked! I can file an issue on the slideover backdrop and link here 🙏
🙌1
Ben M.
·
You’re the best! Thanks
Anthony P.
·
https://github.com/Arize-ai/phoenix/issues/7814