No logs available for gpt-5.1 API call

Hey,

I made a successful API call testing the gpt-5.1 model, I received the desired output but the logs for this particular API key (checked and confirmed) show no activity. I used the chat-completion method, but also searched under other categories. There are no filters set.

I of course tried to log out - log in, but no effect.

Are any of you experiencing the same?

Update 1: Actually I’m not seeing logs for gpt-5 calls either. Must be an ongoing issue.

3 Likes

Seems as expected. The calls I recently allowed to be “store”:“true”, for a specific purpose of verifying for someone on the forum the operation of persistent storage, are also serving the purpose of showing them now:

Then, one chat completion log item also.

Did you have responses events for ranges that you can no longer see, or are you only now having your first look?

Check: https://platform.openai.com/settings/organization/data-controls/data-retention

Then, that you are aware of the platform site’s top-left menu for “organization” → “project”. That needs to be consistent, as the log is filtered and scoped by the selected project.

Chat Completions does not store by default, you’d have to make calls with "store":"true". There is no purpose except for awkward “evals”.

A final thing that could break rights is a new deployment of “roles” for “members” with individual rights to be set, under “people” (when you have people invited and understand the implications). I expect the issue to be found in one of the earlier investigations, though.

IMO: You should not willingly persist data without reason.

The platform site has a listing endpoint that is not available on the API, just to make this feature useless except to OpenAI.


New experiments:

GPT-5.1 API call from platform site with store:true and enabled-per-call:

Result: Nothing new is percolating into the Chat Completions log list immediately.

I asked “o4-mini”, which opined: “Bottom line: Only enable “store”: true for non-sensitive, shareable prompts and responses.” - no new log entry either. So it seems I can replicate expected features not being serviced.

Delays or non-function in “logs” have happened before, or no entries. Workflow currently uninterrupted.

I am experiencing a similar problem, with GPT 4.1 models (mini, nano). My completion API logs are no longer showing up. The last log recorded was on Nov 15th 07:00:00 UTC, I haven’t changed anything in my app, store = true was always set.

I tried the response API using playground and the logs seem to be recorded. Is there a way to try to completion API using playground?

EDIT: Found the toggle to use completion API in playground, and the logs are not showing up for those requests either.

2 Likes

Chat Completions does not store by default, you’d have to make calls with “store”:“true”. There is no purpose except for awkward “evals”.

This is not true. By default the basic logs are stored for 30 days.

Nothing in the configuration and settings has been changed in the last days and today I stopped receiving logs for completion types API calls. Logging for the organization is enabled. I tested GPT-5, so it’s not exclusive for GPT-5.1. I also tested different API keys within the same organization. This must have been a change on the side of OpenAI or something was changed for the organizations in general.

The timing is similar to where my logs stopped too.

3 Likes

“This is not true” is not true.

Responses: “store” defaults to “true”;
Chat Completions: “store” defaults to “false”.

The only thing where “default” may have a different answer for you is the state of Data Controls“API call logging”. On your particular organization, your default could depend on the org age and when this feature was migrated in (or forgotten changing). I have another org, where enabled per call is set from not being changed. Another org still also is “enabled per call”. Meaning: “store”:“true” must be sent in a Chat Completions call for logging; “Per call” is “not unless requested”.

Options are [“disabled”, “enabled per call”, “enabled for all projects”] until you create multiple projects.

Evidence: I have a single Chat Completions API call in logs, specifically there because I needed to see on Oct 17. It better be gone tomorrow. I can assure you I’m making more Chat Completions API calls than that!

The newest call still has not shown up, confirming the issue with storing or retrieving requested API calls to the “logs” listing endpoint.

2 Likes

Well I’m speaking of months of experience of running API calls this way without bothering to set up “store” object - the logs were there by default.

I’m not here to argue but to find a solution, so I added the “store” parameter set to true to the request body of the API call as per documentation: https://platform.openai.com/docs/api-reference/chat/create#chat_create-store

No logs are available for that chat completion.

At the same time I noticed a random log showing up in the list from Saturday afternoon, that wasn’t there when I made this thread. Still no logs from yesterday or today. It looks very much as a problem with logging on the OpenAI side, not with the configuration or using store parameter in the API calls.

Yeah, having same issues.

Logs stopped on chat completions on Saturday 15th of November 2025.

Just run playground test with ‘store’=true.For responses logs are there but not for chat completions.

3 Likes

Hello everyone, Apologies for the inconvenience. We have flagged this to our engineering team and will get back to you all with an update very soon. Thank you!

5 Likes

Hello support team, any update? :slight_smile:

1 Like

Ping !

I still do not see logs. Some logs showed up from 17th, but nothing since then and it looks like a problem has been forgotten…

1 Like

It seems that the logs are appearing gradually… I did not have logs since Nov 15th, but now I do not have logs since Nov 17th…

2 Likes

I can confirm the past logs are available and new are showing up right away after making an API call.

The issue looks solved at least for me. Thanks.

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.