Updated June 2026
When your ChatGPT custom instructions aren’t working as expected, it can be frustrating. This guide provides direct, actionable steps to troubleshoot and resolve common issues, getting your AI assistant back on track.
⚡ Quick fix
- Start with verify custom instructions are enabled and set up correctly.
- Start with clear browser data or switch browsers.
- Start with analyze instruction conflicts and specificity.
- Start with check chatgpt service status and account issues.
What this problem means
When your ChatGPT custom instructions aren’t working as expected, it can be frustrating. This guide provides direct, actionable steps to troubleshoot and resolve common issues, getting your AI assistant back on track.
Verify Custom Instructions are Enabled and Set Up Correctly
Why this happens: The most common reason is that the feature isn’t activated, or the instructions contain syntax errors, formatting issues, or are simply not saved properly.
- Access Settings: Click on your profile icon (usually bottom-left) in ChatGPT.
- Navigate to Custom Instructions: Select “Custom Instructions” from the menu.
- Enable Feature: Ensure the toggle switch for “Custom instructions” is set to ON (it should be green or blue, indicating active).
- Review Content: Carefully read through “What would you like ChatGPT to know about you to provide better responses?” and “How would you like ChatGPT to respond?”. Check for typos, missing punctuation, or overly complex statements that might confuse the AI.
- Save Changes: Always click the “Save” button after making any adjustments.
Clear Browser Data or Switch Browsers
Why this happens: Corrupted browser cache, old cookies, or extensions can interfere with how web applications like ChatGPT function, preventing settings from loading or applying correctly.
- Clear Cache and Cookies:
- Chrome: Go to
Settings > Privacy and security > Clear browsing data. Select “Cached images and files” and “Cookies and other site data,” then click “Clear data.” - Firefox: Go to
Settings > Privacy & Security. Under “Cookies and Site Data,” click “Clear Data.” Check both options. - Edge: Go to
Settings > Privacy, search, and services. Under “Clear browsing data,” click “Choose what to clear.” Select cache and cookies.
- Chrome: Go to
- Try Incognito/Private Mode: Open ChatGPT in your browser’s incognito (Chrome, Edge) or private (Firefox, Safari) window. This bypasses most extensions and cached data.
- Use a Different Browser: If the issue persists, try accessing ChatGPT from an entirely different browser (e.g., if you use Chrome, try Firefox or Edge).
- Disable Browser Extensions: Temporarily disable browser extensions, especially those related to AI, privacy, or content blocking, as they can sometimes interfere.
Analyze Instruction Conflicts and Specificity
Why this happens: If your custom instructions are too vague, contradictory, or overridden by specific details in your prompt, ChatGPT may ignore them or prioritize the most recent, explicit input.
- Simplify Instructions: Reduce your custom instructions to a very basic command, e.g., “Always start your response with ‘Hello there!’” or “Always write in a friendly tone.” Test if this simple instruction works. If it does, gradually reintroduce your full instructions, testing after each addition.
- Check for Contradictions: Ensure your “What to know about you” and “How to respond” sections don’t contradict each other. For example, asking for “concise responses” in one section and “detailed explanations” in another can confuse the model.
- Prompt Specificity: Remember that a specific instruction within your current prompt will usually take precedence over general custom instructions. If you want the custom instructions to apply, ensure your prompt doesn’t explicitly override them.
- Test with New Chats: Custom instructions typically apply to new chats. If you’re testing in an ongoing conversation, they might not fully re-contextualize the AI. Start a fresh chat.
Check ChatGPT Service Status and Account Issues
Why this happens: Sometimes the problem isn’t on your end but with the ChatGPT service itself, or a temporary glitch with your account.
- Check OpenAI Status Page: Visit status.openai.com to see if there are any ongoing service disruptions or outages affecting ChatGPT.
- Log Out and Log In: Simple as it sounds, logging out of your ChatGPT account and then logging back in can often resolve minor authentication or session-related glitches.
- Check Subscription (if applicable): If you’re a ChatGPT Plus subscriber, ensure your subscription is active and there are no payment issues, although custom instructions are generally available to all users.
- Contact Support: If all else fails and the issue persists, consider reaching out to OpenAI support directly through their help center. Provide detailed information about your troubleshooting steps and what you’ve observed.
Diagnostic checklist before you escalate
Most web-app failures can be narrowed to service status, one account session, browser data, an extension, or the network. Test those boundaries in order rather than clearing everything at once. A private window and a second network are especially useful because they change one layer without altering your account data.
- Check the provider’s official status page before changing local settings.
- Hard-refresh, start a new session, and test a private browser window.
- Disable content blockers, privacy extensions, VPN, proxy, and secure DNS temporarily.
- Compare another browser, device, and network to locate the failing boundary.
- Record timestamps, error text, and the smallest reproducible sequence for support.
| Test | What the result tells you | Next move |
|---|---|---|
| Official status page reports an incident | The service is affected beyond your device | Pause local resets and monitor recovery |
| Private window works | Normal browser data or an extension is involved | Clear site data and enable extensions one by one |
| Another network works | DNS, VPN, proxy, firewall, or filtering is involved | Review the original network configuration |
| Failure follows the account everywhere | Account, plan, quota, or service-side state is likely | Collect evidence and contact official support |
Verify the recovery across session and network boundaries
When starts working, repeat the original action in a fresh tab and then in the normal browser profile. Confirm that buttons, uploads, saved history, and live updates behave normally instead of only rendering the first screen. If private mode works but the regular profile fails, continue isolating cookies and extensions rather than declaring the service fixed.
Restore extensions, VPN, proxy, secure DNS, and content filtering one at a time. Reload after each change. This controlled restoration identifies the incompatible layer and prevents the common outcome where everything is disabled permanently. Finish by testing one other device or network so you know whether the recovery belongs to the account, the device, or the connection.
- The original action succeeds twice in a fresh session.
- The normal browser profile works after cleanup.
- Extensions and network controls are restored individually.
- Saved data and account history remain available.
- A second device or network confirms the result.
Keep a short note of the working configuration and the date of the test. Products, models, browser versions, limits, and safety policies change over time, so a previously successful workaround may later become obsolete. Prefer current official documentation over old forum instructions, and reverse temporary diagnostic changes once testing is complete. This gives you a reliable baseline without leaving extensions disabled, security controls weakened, or experimental settings enabled indefinitely. Recheck the baseline after major updates before assuming an older failure has returned for the same reason.
When none of the fixes work
Repeat the smallest failing action once and record the exact local time and time zone. Note the product, model or feature, account plan, browser or app version, operating system, and whether the same action works in a private window, on another device, or on another network. This evidence is much more useful than saying the tool is “still broken.”
Use the provider’s official support channel. Include a screenshot with sensitive information removed and list the steps already tested. For developer tools, add sanitized request and response details, correlation IDs, and SDK versions. Never send passwords, one-time codes, API keys, session cookies, private repository contents, or complete payment information.
Frequently Asked Questions
Q: Do custom instructions apply to old chats?
A: No, custom instructions generally apply to new conversations. They set the context for future interactions, not past ones.
Q: Is there a character limit for custom instructions?
A: Yes, each section (“What would you like ChatGPT to know about you?” and “How would you like ChatGPT to respond?”) has a limit of 1500 characters.
Q: Why do my custom instructions seem to be ignored sometimes?
A: They might be overridden by a very specific instruction in your current prompt, or they could be too vague or contradictory. Always aim for clarity and conciseness, and test with new chats.
To fix ChatGPT custom instructions not working, verify settings, clear browser data, refine instruction clarity, and check for service outages.
Bottom line: Work from the least disruptive test to the most specific one. Confirm service health, isolate session and network variables, then escalate with clean evidence instead of repeating the same failing action.
Leave a Reply