I would like to ask whether OpenAI has an official policy or response standard regarding cases where Pulse output is inconsistent for users who have their device language and app language set to a specific non-English language.
More specifically, I am referring to situations where Pulse sometimes appears in the intended target language, but at other times appears in English without any apparent change in user settings.
I am not asking here about individual troubleshooting steps. I am more interested in the broader issue:
Have other users experienced similar inconsistency with a specific non-English language?
Has OpenAI publicly acknowledged this as a known localization or language-selection issue?
Is there any official guidance on whether this is treated as a user-side settings issue or as a system-side behavior issue?
If multiple reports exist, what is OpenAI’s standard process for addressing them?
I would appreciate any information from other users, moderators, or OpenAI staff regarding whether this has already been recognized and what the official handling policy is.
I’m not aware of a public policy or formal statement specifically covering inconsistent Pulse language behavior.
Language output can be influenced by a mix of factors like device settings, app language, and context, so occasional inconsistencies can happen, especially in non-English scenarios. I haven’t seen this called out as a widely acknowledged issue specific to Pulse.
If this can be consistently reproduced across users, it would typically be treated as a system-side behavior and looked into further. Sharing a few concrete examples would help clarify whether this is a broader pattern.
However, I must respectfully disagree with the explanation that “language output can be influenced by a mix of factors like device settings, app language, and context.”
My situation is as follows:
My ChatGPT account language is explicitly set to Korean in the settings.
Both my PC web version and my Galaxy S24 Ultra (Android app — always kept at the latest version) have Korean set as the system language.
I submit queries in Korean approximately 99% of the time. Even on the rare occasions when I upload an English document for reference, I still write the actual question in Korean.
Despite all of the above, the daily Pulse notification is delivered in English on completely random dates with no correlation to content, context, or my query language. For example, in the period I have tracked (since March 21), it arrived in English only on:
March 24, April 3, April 11, April 13, April 14, and April 15.
All other days it correctly arrived in Korean.
This behavior completely ignores the account language I have explicitly set and appears to be decided by some internal, opaque logic that you yourself described as “a mix of factors.” By acknowledging that the output is not strictly following the user’s account language setting, your response essentially confirms that there is a flaw in OpenAI’s language-determination logic for Pulse.
This is not a user-side issue (device, app version, cache, or settings) — it is a clear system-side bug. As a ChatGPT Pro subscriber paying $220 per month, receiving a daily feature in the wrong language at random is extremely frustrating and undermines the value of the product.
I kindly ask that this be escalated to the engineering team as a reproducible bug rather than treated as occasional “inconsistency.”
Thank you for your attention. I look forward to a proper resolution.
I checked on this, and it looks like you already have a support ticket open for the issue, so you’re in the right place. Given everything you shared, this does look like something inconsistent rather than a setup issue, and the specific dates you tracked are especially helpful.
Since we’ve asked for a bit more detail above, once you’re able to share that, it should help get this looked at more closely. Really appreciate you taking the time to document the behavior so clearly.
If you notice any new patterns or changes in the meantime, feel free to share them here as well.
I refused to disclose the app version and device model. The reason is that it appears you are trying to limit this issue to a specific app version and device. I clearly stated that I am using the latest version as of the time of writing. Furthermore, this issue is not unique to the current version; it has persisted despite multiple app updates over the past month. Please stop asking me about the app version. You know better than anyone when and to which version the app was updated. My main device is a Samsung Galaxy S24 Ultra. However, I strongly reiterate that this is not a problem limited to this device.