Open janitaportrait opened 1 month ago
Hi @janitaportrait could you confirm a couple things for us:
Just checked and can confirm that a run with id 8b45061a-1221-42d0-88a3-6ef170fd564b
exists in the DB. We haven't experienced a data loss event
When I said "all of the traces appeared empty", I meant that I can still see the names of the traces, but there is no data attached to them. I am suspecting it is a UI issue because when I retrieved the same traces with the SDK, I could see their data. Please see attached screenshot. The input and output fields are empty, whereas on the previous day the input and output fields were displaying my logged data as well as the nested LLM calls.
This is from another run using the same tracing code, ie this is what I would expect the traces to look like:
Thanks for clarifying - if you pick "Raw Input" by clicking the dropdown there, does it still show as empty? Or is there content present in the raw payload that is being mis-typed by our frontend?
The raw input and raw output also appear empty
@janitaportrait was trying to debug this. I may have pushed a fix for it in the latest SDK release. LMK if you still run into issues
I created traces for a project, logging both the nested llm call and the inputs / outputs of the function. I saw the data appear in the dashboard, but when I checked the next day, all of the traces appeared empty and there was no longer any data. Here's an example run ID from the project in question:
8b45061a-1221-42d0-88a3-6ef170fd564b
This is pretty concerning as I'm not sure I can rely on my data being accessible / viewable. Please let me know how this can be addressed. Appreciate the help, thank you!
Suggestion:
using my run ID, please clarify if there is a rendering issue preventing the data from showing up, or if it is a data loss issue