Issue with Session Track Access: Need Assistance

anki y.

·Oct 14, 2025 07:02 AM·

Hi team, I got this message when I clicked on a session track.👀

7 comments

· Sorted by Oldest

RunLLM
APP
·
·
If you received an error or unexpected message when clicking on a session track in Phoenix, it may be due to a known UI or backend limitation, such as session errors when traces are missing output, UI bugs in older versions, or pagination limits (e.g., only 50 traces shown per session in some versions). For example, in Phoenix 7.1.0, sessions with errors or missing outputs could not be accessed until all traces were deleted, but this was fixed in 7.2.0. In versions before 11.2.0, the UI only displayed the first 50 traces per session due to lack of frontend pagination, which has since been addressed in newer releases. If you see a "Something went wrong" or similar error, upgrading to the latest Phoenix version is recommended, and clearing your browser cache may also help if the UI fails to load due to schema changes or caching issues. If you can provide the exact error message or a screenshot, I can give more targeted troubleshooting steps or confirm if it's a known issue with a specific fix or workaround. Would you like more detail or help with a specific error message? Sources: - <https://github.com/Arize-ai/phoenix/issues/5750|Phoenix issue: Sessions cannot be accessed after error, fixed in 7.2.0> - <https://github.com/Arize-ai/phoenix/issues/8325|Phoenix issue: Session UI only shows 50 traces, fixed in 11.2.0> - <https://github.com/Arize-ai/phoenix/issues/3384|Phoenix issue: UI errors due to browser cache>
💡 Hint: Mention RunLLM in the thread for followups.
Anthony P.
·
·
Can you share your phoenix version please? Any details that could help us replicate would also be great
RunLLM
APP
·
·
If you tell me the right answer to this question, I'll make sure I don't make the same mistake twice!
Feedback
Type the right answer here...
↵ Please 'enter' to submit
Anthony P.
·
·
I was able to reproduce on the latest version of phoenix, I will look into this
👀1
Anthony P.
·
·
This has been fixed and released in Phoenix v12.6.1 Sorry about the disruption!
👀1

anki y.

Hi Tony, Thanks for the quick response! I updated to Phoenix v12.6.1, but I'm still encountering the same error in the Sessions UI

Error fetching GraphQL query 'sessionLoaderQuery' with variables '{"id":"0"}': 
[{"message":"an unexpected error occurred","locations":[{"line":4,"column":3}],"path":["session"]}]

current versions:

- arize-phoenix: 12.6.1
- arize-phoenix-client: 1.21.0
- arize-phoenix-otel: 0.13.0
- openinference-instrumentation: 0.1.40
- openinference-instrumentation-autogen-agentchat: 0.1.5
- openinference-instrumentation-openai: 0.1.39
- openinference-semantic-conventions: 0.1.23

and my implementation follows the pattern:

tracer = trace.get_tracer(__name__)

with tracer.start_as_current_span(
    "query_request",
    attributes={
        SpanAttributes.OPENINFERENCE_SPAN_KIND: OpenInferenceSpanKindValues.CHAIN.value,
        SpanAttributes.SESSION_ID: session_id, 
        SpanAttributes.INPUT_VALUE: message,
    }
) as root_span:
    with using_session(session_id):
        # Child spans here
        root_span.set_status(Status(StatusCode.OK))
```

The traces appear correctly in Phoenix, and I can see the session.id attribute, but the Sessions page shows the GraphQL error. Could you provide a minimal sample script to help me verify if the issue is with my code or still on the Cloud, 😀

Anthony P.
·
·
Can you try performing a hard refresh of the browser and try again? I can see the original bug in the error message still. The wrong id (0) was making it into the url
👀1

RunLLM
APP
·
·
If you received an error or unexpected message when clicking on a session track in Phoenix, it may be due to a known UI or backend limitation, such as session errors when traces are missing output, UI bugs in older versions, or pagination limits (e.g., only 50 traces shown per session in some versions). For example, in Phoenix 7.1.0, sessions with errors or missing outputs could not be accessed until all traces were deleted, but this was fixed in 7.2.0. In versions before 11.2.0, the UI only displayed the first 50 traces per session due to lack of frontend pagination, which has since been addressed in newer releases. If you see a "Something went wrong" or similar error, upgrading to the latest Phoenix version is recommended, and clearing your browser cache may also help if the UI fails to load due to schema changes or caching issues. If you can provide the exact error message or a screenshot, I can give more targeted troubleshooting steps or confirm if it's a known issue with a specific fix or workaround. Would you like more detail or help with a specific error message? Sources: - <https://github.com/Arize-ai/phoenix/issues/5750|Phoenix issue: Sessions cannot be accessed after error, fixed in 7.2.0> - <https://github.com/Arize-ai/phoenix/issues/8325|Phoenix issue: Session UI only shows 50 traces, fixed in 11.2.0> - <https://github.com/Arize-ai/phoenix/issues/3384|Phoenix issue: UI errors due to browser cache>
💡 Hint: Mention RunLLM in the thread for followups.
Anthony P.
·
·
Can you share your phoenix version please? Any details that could help us replicate would also be great
RunLLM
APP
·
·
If you tell me the right answer to this question, I'll make sure I don't make the same mistake twice!
Feedback
Type the right answer here...
↵ Please 'enter' to submit
Anthony P.
·
·
I was able to reproduce on the latest version of phoenix, I will look into this
👀1
Anthony P.
·
·
This has been fixed and released in Phoenix v12.6.1 Sorry about the disruption!
👀1

anki y.

Hi Tony, Thanks for the quick response! I updated to Phoenix v12.6.1, but I'm still encountering the same error in the Sessions UI

Error fetching GraphQL query 'sessionLoaderQuery' with variables '{"id":"0"}': 
[{"message":"an unexpected error occurred","locations":[{"line":4,"column":3}],"path":["session"]}]

current versions:

- arize-phoenix: 12.6.1
- arize-phoenix-client: 1.21.0
- arize-phoenix-otel: 0.13.0
- openinference-instrumentation: 0.1.40
- openinference-instrumentation-autogen-agentchat: 0.1.5
- openinference-instrumentation-openai: 0.1.39
- openinference-semantic-conventions: 0.1.23

and my implementation follows the pattern:

tracer = trace.get_tracer(__name__)

with tracer.start_as_current_span(
    "query_request",
    attributes={
        SpanAttributes.OPENINFERENCE_SPAN_KIND: OpenInferenceSpanKindValues.CHAIN.value,
        SpanAttributes.SESSION_ID: session_id, 
        SpanAttributes.INPUT_VALUE: message,
    }
) as root_span:
    with using_session(session_id):
        # Child spans here
        root_span.set_status(Status(StatusCode.OK))
```

Anthony P.
·
·
Can you try performing a hard refresh of the browser and try again? I can see the original bug in the error message still. The wrong id (0) was making it into the url
👀1