Helicone Community Page

Updated 2 years ago

My dashboard of requests is consistently delayed by about 48 hours

Is this intended? My account might be in a weird state since I signed up really early.
b
S
J
8 comments
Hey , thanks for signing up really early πŸ™Œ

Delay by 48hrs is weird - is it that requests only show up 48hrs after they happen?

Have you made the auth transition and added the helicone api key to your requests? https://www.helicone.ai/auth-transition
it's not a consistent 48 hours but last requests I'm seeing are from 5/23 2pm ET so roughly 50 hours ago
I've been waiting on an update to an OSS library to make the switch on the auth. Will that make a differnce?
Requests that aren't authenticated with the Helicone-Auth header will not be logged, we did this for security reasons to better protect your data. The Helicone API will never stop forwarding to openai though, so don't worry about your endpoint not working.

Any way we can help out with that OSS library so you can make the switch sooner?
That'd be great. Got any rubyists locally? Here's the issue

https://github.com/alexrudall/ruby-openai/issues/266

this one is related
https://github.com/alexrudall/ruby-openai/issues/255

This is the main openai ruby client and it just switched over to a new HTTP library under the hood. Exposing some more configuration and visibility on the request/responses has been on my backlog for awhile
ah that first one was for caching but same approach in adding a header
btw, this seemed to have gotten better. I also forked that library for my own purposes so have caching and auth working as well πŸ‘
awesome! Thanks for getting back to us - We just shipped a pretty large change to the dashboard and re-wrote how we manage timezones.
Add a reply
Sign up and join the conversation on Discord