Me making those screenshots was after making Chat Completions calls that should have appeared. The API calls are not appearing. I don’t see churning nothing, though: check what “responses” looks like, with its logged calls persisting forever unless you logged IDs and manually delete them.
The logs not working, not showing API calls for days on end, taking a week to get a “we implemented a change” fix of what was magically broken, has happened multiple times in the past, and as expected, happens again now, proving that you should not trust this feature nor invest time in calls for “evals”, just as nobody used the poor “distillation” that was also to be based on logged API calls.
Besides what’s already been explained, I’m also adding these docs, so you can check if any of these might be of help.
Stored Chat Completions API reference:
Migration guide mentioning storage behavior for Responses / Chat Completions:
Data retention / Zero Data Retention controls:
From those docs, I’d check:
whether your requests are actually being made with store: true
whether API call logging is enabled for the org/project
whether Zero Data Retention is enabled, since that would make store behave as false
whether the same issue happens in another browser/incognito, in case this is only a Dashboard UI loading issue
If stored calls should exist but the Completions tab keeps shimmer-loading or returning empty, then it sounds like something Support/OpenAI staff would need to inspect.
Add: Just adding one more data point here: on my side, the Logs → Completions tab is currently loading and showing stored entries.
Did you tried loading it with thousands of requests/completions? because I think that’s the problem. It loaded fine when the requests were below 100. now I have ~5k request..and it just showing empty page with shimmer loading.
So at least in my case, 100 stored completions did not reproduce the shimmer-loading/empty page issue.
Of course, that does not rule out a scaling issue around thousands of stored completions, since your case is closer to ~5k requests. But it may suggest the problem appears only at a higher volume or may be account/project/browser-specific.
If it still doesn’t appear for you, I’d suggest contacting the Help Center and opening a support ticket so they can investigate it on the account/project side. From my test, I can’t reproduce it at 100 stored completions, so your case may require them to check the specific project/account behavior.