ChatGPT Response Cuts Off Mid-Sentence — Why and the Fastest Fix
When ChatGPT stops mid-output, the cause is usually max output tokens, a structural choice the model made, or a transient stream drop — in that order.
Articles tagged with #Debug
When ChatGPT stops mid-output, the cause is usually max output tokens, a structural choice the model made, or a transient stream drop — in that order.
You started changing the account email, got logged out, and now neither the old nor new email lets you back in. The verification link is the only way through. Recover without losing chats.
The reply streams half a sentence then just freezes. Usually a dropped SSE connection, a tab suspension, or a backend hiccup. Here is how to diagnose and recover.
You upload a PDF or image and Claude shows the attachment tile but no preview thumbnail. Usually a CDN race, MIME mismatch, or browser cache — here is how to fix it.
Click a citation link, hit a 404 or land on the wrong article. Usually URL paraphrasing, expired snippets, or paywalls — how to verify sources and rescue the underlying fact.
A PreToolUse hook keeps rejecting Edit calls with no clear reason, including safe edits. Usually exit-code logic, stdin parsing, or matcher scope at fault.
MCP tool calls (filesystem, GitHub, custom) time out in Claude Code, but a direct curl to the server works. Usually transport, stdio framing, or response shape.
A long agent reply gets cut off mid-sentence under context pressure. Usually compaction, max_tokens cap, or runaway tool output eating the budget.
You close Cursor, reopen it, and the chat or Composer history is empty or shows only the last thread. Usually storage corruption, sync issues, or workspace mismatch. Recover and prevent.
You hit Cmd-K, type the change, and the inline popup spins forever. No diff, no commit, no error. Usually network, model, or context. Walk the four root causes.
The Extensions panel in Cursor returns a network error or an empty list. Cursor uses Open VSX, not Microsoft's marketplace. Configure the right gallery and unblock the install.
You added an MCP server in Cursor settings but it shows disconnected, or the tools never appear in Composer. Usually transport, path, or schema. Diagnose and fix in five minutes.
Agent mode keeps running shell commands without the confirm prompt, even when you flipped the toggle off. Usually allowlist scope, stale settings, or a workspace override. Fix it.
Upload a CSV and ChatGPT lists weird columns, merges two into one, or treats the header row as data — delimiter detection is the usual culprit.
Upload an XLSX and ChatGPT reports cell values fine — but anything formula-driven comes back as a literal string like '=SUM(A1:A10)'. Here is why and how to fix.
You replaced the file but ChatGPT keeps quoting the old version — cache, duplicate filenames, and chat history are the usual culprits.
Scanned or handwritten PDFs return 'no text found' or hallucinated content — the built-in extractor only reads the text layer. Fix with an OCR pre-pass.
Upload a big spreadsheet, ask 'how many rows are there,' and ChatGPT confidently says 1000 — token-budget truncation. Here is how to analyze the whole file.
Upload a ZIP and ChatGPT only sees the filename — never extracts. File-type filtering and sandbox rules block automatic unzipping. Here is the workaround.
Chrome rejects an otherwise valid cert with NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED. The cert was issued but never logged to CT, or its SCTs are bad.
Toggling Cloudflare's proxy on or off changes whether traffic hits the edge or the origin. The wrong state breaks SSL, WebSockets, or apex CNAMEs subtly.
Cursor picks the system Python instead of your project venv, breaking imports, linting, and agent-generated code. Diagnose the interpreter picker, venv discovery, and shell PATH.
Cursor's SSH Remote session disconnects while you are editing, losing the agent context and unsaved buffer state. Diagnose the keepalive, network, and remote extension host.
You turned on DNSSEC and resolvers now return SERVFAIL. The DS at the registrar does not match the DNSKEY at your nameservers, breaking the chain.
IPv4 users reach the site fine but IPv6 users get timeouts. Either AAAA is absent, points to a dead address, or your firewall blocks v6. Fix dual-stack.
You delegated a subdomain to its own nameservers but resolution fails. The parent zone needs glue A/AAAA when NS targets live inside the subzone.
Encrypted PDF uploads succeed visually but ChatGPT answers as if the file is empty. The rejection is silent — no error banner, just hollow replies.
Upload a JSON file expecting ChatGPT to query keys and aggregate values. It instead reads the file as a wall of text and answers by string-matching.
Monthly quota gone in a day — rerolls, parallel jobs, and HD mode burn the fastest.
A normal-looking prompt gets refused — one word tripped the filter and you didn't notice.
Subject lit from the left, sun on the right, shadows pointing nowhere consistent. Pin one key light + direction + time of day.
You wanted photographic, got CGI-looking plastic. Three real causes: render keywords in prompt, wrong checkpoint, and CFG too high.
Colors look like a billboard — style words, CFG, and color LoRAs stack into a neon disaster. Strip the boosters first, then bring saturation back in post.
Skin looks waxy, jaundiced, over-smoothed, or doll-like. Beauty LoRAs, color-cast lighting, and missing negatives are the usual culprits.
Arm bends backward, neck twists wrong. Use concrete action verbs, feed an OpenPose skeleton via ControlNet, and pull the camera back.
A watermark-shaped smudge or garbled signature in the corner — training data residue. Negative prompt it, crop it, and pick a cleaner checkpoint.
Table has no horizon, stairs face the wrong way, head-to-body ratio is off. Add focal length + viewpoint + perspective style to the prompt opening.
You asked for a library, it gave one that's been abandoned 4 years — training cutoff + no registry check.
All green, ship it, prod breaks — tests covered the happy path only, mocks shielded real branches.
Last second cuts to black before the motion completes — caused by missing ending beat in prompt, too-short duration, or no end-frame reference.
Two clips feel hand-cut with scissors. Match end-pose of clip A to start-pose of clip B, add an editorial dissolve, and use J/L cuts in post.
Same shot, but the tint suddenly turns colder or redder. The model re-guesses color temperature between frames — pin it with a Kelvin spec and unify in post.
Hat in clip 1, no hat in clip 2 — multi-clip generation has no shared anchor. Use a wardrobe / props sheet and reuse one reference image.
A few seconds go black mid-clip, or the file freezes. Causes are codec/container mismatches, generation timeouts, and tier-limit truncation.
30 minutes in, no progress. Cancel stuck jobs, check concurrency caps, submit at off-peak UTC hours, or fall back to another platform.
`.env` or API key swept into a commit by `git add .`. Rotate first (always), then prevent: ban broad `git add`, install secret scanner, gitignore.
Finishes the task, also adds 5 "might be useful later" utility functions nobody calls. Bound scope in the prompt and in CLAUDE.md, delete on review.
Agent makes tests green by adding `.skip`, deleting assertions, or broadening matchers. Forbid test edits, scan diff for skip markers, treat test changes as a separate PR.
Firestore writes / Functions calls / Hosting bandwidth — each has a hard line on free tier.
`FAILED_PRECONDITION: The query requires an index` — multi-field where + orderBy demands a composite index.
First request takes 2–5s — Deno isolate not warm, heavy imports, external API call.
`error: remaining connection slots are reserved` — Serverless code hitting raw Postgres.
The visible "Published / Updated" date does not match `datePublished` / `dateModified` in JSON-LD. Why this is more than a cosmetic bug.
Rich Results Test passes but Search Console flags breadcrumb mismatches, or the breadcrumb in SERP looks wrong. How to align JSON-LD with what users see.
You set canonical to a new URL. Weeks later, Google still ranks the old URL. Why canonical is a hint, not a command, and what actually changes the chosen canonical.
Search Console "HTML Improvements" or a third-party crawl shows the same meta description on hundreds of pages. Why this matters less than people think, but still matters.
Rich Results Test errors on FAQPage. Search Console removes FAQ rich snippets. Common causes and fixes.
You set hreflang for en and zh, but Search Console flags missing x-default. What x-default actually does and when you need it.
When `<meta name="robots">` and `X-Robots-Tag` HTTP header conflict, results are unpredictable. How to decide which to use and how to keep them in sync.
You added `<meta name="robots" content="noindex">` weeks ago but the page is still in Google. The most common reasons.
A template default or migration mistake left `<meta name="robots" content="noindex">` on pages that should be public. Detection and rollback.
Sitemap.xml lists URLs that have `<meta name="robots" content="noindex">`. Google reports them, but inconsistently. Why this happens and how to fix.
A template refactor or framework upgrade broke JSON-LD blocks site-wide. How to detect and fix.
Sharing your URL on X/Twitter shows no image, even though og:image is set. Why Twitter cards have their own rules.
You added VideoObject JSON-LD for embedded videos but no video rich result, no video tab listing. Why.
The site-level WebSite JSON-LD declares name / URL / SearchAction that don't match reality. Why this confuses Google and how to align it.
Your host says use A; another doc says CNAME. Records conflict and site doesn't resolve.
Code is on the page but no ads appear. Common causes after approval.
Troubleshoot the common AdSense placement problems — clutter, double-stacked units, layout shift — when Auto Ads and manual placements conflict. For the strategic comparison, see the linked guide.
Rejected for low-value content. What it actually means and the recovery path.
"No ad to display" appears in inspector. Inventory, page topic, or country.
Got a policy violation warning. Read it carefully, act fast.
Script loaded, but ad slots empty for hours. Slot config or page eligibility.
You submitted and got "needs review." This is the normal initial state, but here's what to do during wait.
CWV scores tanked after adding AdSense. Usual causes: ad script blocking render; cumulative layout shift from ads loading; too many ad slots above the fold. Start with: defer or async the ad script.
Agent keeps trying the same fix or oscillates between two states. Break the loop fast.
Code is reverted, but the agent left behind: stale `dist/`, an applied migration, dangling feature flags, mutated state in third-party tools. Roll back by domain, not by `git reset`.
Cut between two AI clips feels jarring — match motion, color, and pacing.
Classic case: AI added a dep without committing the lockfile, or relied on a local Node version.
After an AI run, npm run build fails. Diagnose with diff review, type-checking, and selective revert.
Agent rewrote .env with placeholders or removed entries — recover and prevent.
Six-finger hands are still common. Negative prompts + targeted regeneration.
Agent imports `src/utils/superhelper.ts` that was never created — common, fixable.
You asked for anime, model leaks photoreal skin, eyes, or lighting. Anchor with a specific anime reference and strip realism cues.
Background steals attention from the subject. Pick a background style intentionally — minimal gradient, controlled bokeh, or solid color anchor.
Same character description, different face every time. Use a reference image, lock the seed, and describe distinctive identity markers.
Too many objects fighting for attention. Reduce the subject list to one hero, add negative space, and use depth-of-field to push the rest back.
Image looks blurry, soft, or low-detail. Three real causes: too few pixels, too few sampler steps, and a prompt with no detail anchors.
Model ignores big chunks of your prompt — usually prompt order, weight, or contradiction.
Subject looks flat, harsh, or amateur. Cinematography vocabulary (key + fill + rim, direction, quality, temperature) beats adjectives every time.
AI-generated series images drift in style across every shot. Six controllable methods — style header prompts, seed locking, style reference, palette limits, LoRA, and image-to-image chaining.
You need 5 cohesive images and got 5 unrelated ones. Lock a style anchor sentence, reuse one reference image, and pin the seed.
Start with image A, end with someone else. Motion strength + identity anchors fix it.
You set 9:16, output came 1:1. Tool-specific param syntax, model support, and override defaults — each platform handles aspect differently.
Mouth movements don't match the audio you generated separately.
Your branch + AI edits conflict with main. Resolve without losing AI improvements.
Agent ran an install or removed deps and now your lockfile is at war with the team's.
Realistic prompts come out plastic-looking. Cause: lighting and skin/material cues.
Studio shot AI prompts often produce uncanny products. Lighting, lens, and surface cues are the fix.
Agent created `UserList2.tsx` next to the original or scattered duplicates. How to clean up safely.
AI "simplified" code and quietly removed a branch your users actually rely on.
Three commands cover 99% of rollback scenarios: stash, restore, reflog.
AI produces code that doesn't type-check — usually wrong types, any-casts, or missing generic parameters.
Models still struggle with text-in-image. Two strategies: short words or post-edit.
Background flickers between styles or shapes. Causes: prompt fight, motion strength, model.
Static shot prompts come out shaky. Most AI tools default to gentle handheld motion unless you explicitly say 'locked tripod' — and motion sliders need to go to zero.
Same character mid-clip but their features morph. Keep clips ≤4s, lock a canonical reference image, and drop motion strength a notch.
Face is fine at frame 1, different by frame 60. The model's identity coherence window is ~3-4 seconds — anchor with a reference image, shorten clips, drop motion.
Output looks nothing like the input image. Raise image strength, shrink the text prompt, and ensure source is ≥1024px with subject filling >40% of frame.
AI video models break motion: extra fingers, faces morphing, objects vanishing. These are universal weaknesses. Seven actionable methods to make Sora, Veo, Kling, and Runway clips far more consistent.
Subject runs forward but legs go backward, hands phase through objects, balls fall up. Action verbs are ambiguous and physics need explicit spelling out.
Subjects pop in and out across frames. Causes: too many actions, bad start/end pose, low fps.
Everything moves at once and the clip feels chaotic. Drop motion strength, strip extra verbs, and pick exactly ONE moving element (camera OR subject).
Clips drag or rush. Keep clips 2-4s, cut on beats in an NLE, and vary clip lengths on the timeline so it doesn't read as a slideshow.
Bottle stretches, packaging warps, logo bends. Treat product shots like macro photography — high-quality reference, minimum motion, short clips.
Same scene description, two different rooms. Establish a scene anchor: one canonical wide shot, identical lighting language, shared props list.
Person turns into someone else half way through. Identity anchoring helps.
Your AI video is a still with 5-pixel parallax. Add strong verbs, raise motion strength, and name a camera move — the three fixes for under-motion.
Liquid pours sideways, cloth defies gravity, balls roll uphill. Models have limited physics understanding — work around it by avoiding hero physics shots.
Subject dead-center, no depth, no leading lines. Composition cues fix it.
Pages exist in dev but 404 in prod — almost always `build.format`, trailing slash, or output mode mismatch.
Sign-in flow redirects to localhost or the wrong domain. Configure allowed redirect URIs.
Switched domains but old canonical still appears — config + cache.
Bilingual / multi-locale pages have canonicals pointing the wrong direction.
Switched accounts in the UI but ChatGPT still shows the old one — usually cached session, cookie scope, or Workspace lock.
Conversation visible on web but missing in the app (or vice versa)? Three things to check.
Login completes, redirects to chatgpt.com, then a white page. Almost always script load failure, a stuck service worker, or extension conflict.
Third-party cookie blocks break the Auth0 handshake — exact toggles per browser to get login working again.
Numbers come back wrong, headers misaligned, dates flipped — the data toolchain has quirks. Here's how to keep results accurate.
You asked for analysis, got bullet points that anyone could write without reading the file. The fix is prompting for evidence, not the model.
You uploaded a file, asked a question, and now the file is gone from the chat. Whether it's actually gone — or just out of context — depends on where it was attached.
ChatGPT rejects your file or says it can't analyze it. Conversion is almost always faster than fighting the type.
ChatGPT file upload stuck at 0%, fails after the progress bar finishes, or uploads but says 'can't read'? These are different issues. Nine causes and matching fixes.
ChatGPT created a file but the download link 404s, hangs, or comes back empty. Usually session expiry, plan gating, or sandbox timeout.
Click a GPT and nothing loads, or actions silently fail? This is almost always cache, login state, or a broken action manifest.
History gone from the sidebar? Walk this 5-step recovery before assuming the chats are lost.
Image generation refuses to produce output? Quota, safety filter, prompt language, or model availability — in that order.
You uploaded a screenshot or chart and ChatGPT describes it wrong. Usually resolution, OCR limits, contrast, or vague prompting.
200-page report uploaded, but the summary feels like it only read 30 pages. The model is "skimming" — force depth with chunked queries.
Credentials and SSO succeed but the page bounces back to login. 90% of the time it's cookies, third-party storage, or a stale session.
Chrome works, Safari fails (or any other pair). The account is fine — differences live in cookie policy, extensions, and version.
You told ChatGPT something, it says "got it," and then forgets next session? Check these four things.
Hit the "you've reached your limit" wall? Here's what the windowed cap actually means and how to avoid it.
Same email, same password but mobile and web are clearly on different accounts — workspace, SSO method, App Store subscription are the 3 big causes.
You uploaded 3 files expecting comparison, but ChatGPT only references one. Cross-file synthesis needs explicit instruction.
ChatGPT showing 'network error' or 'There was an error generating a response'? It's not one issue, it's eight different ones. Here's a quick triage and fix list in order of likelihood.
Hit Forgot password and nothing came — different flow from signup verification, stricter rate limit, and SSO-only accounts are silently rejected.
Upload a PDF and ChatGPT says it sees nothing — almost always size, scan-vs-text, or extraction layer.
You wrote detailed Project Instructions and ChatGPT keeps ignoring them mid-conversation. The cause is usually instruction weight, conflict with the message, or a Projects-feature limitation.
You uploaded files to a Project but ChatGPT acts like they don't exist. The cause is usually filename signal, retrieval scope, or query phrasing.
You set instructions and files in a Project, but a chat inside the Project ignores them. Here's how the two scopes really interact.
ChatGPT keeps logging you out mid-conversation — cookies being wiped, multiple tabs racing, and corporate proxy stripping headers are the 3 main causes.
A shared chat link 404s or shows blank — almost always sharer-side, not viewer-side.
A shared link is a read-only snapshot, not logging into the chat — here's the function, URL pattern, and the common confusions explained.
When ChatGPT replies are crawling, the cause is usually long context, model mismatch, or network RTT — in that order.
ChatGPT shows 'thinking' or a spinner that never returns? It's not one issue, it's six. Here's a 1-minute triage and the matching fixes for each cause.
The fastest way to clear the IP-triggered safety check without losing the account.
PDF uploaded fine but ChatGPT misses tables, skips pages, or hallucinates numbers. The fix is almost always extraction layer, not the model.
Signup or login verification email isn't coming? Spam, alias filters, corporate ATP, regional delays, or a typo — usually one of these.
Voice mode silent, stuck on listening, or refusing to start? The fix is almost always one of microphone permission, region, or app channel.
Web search shows but never returns results, or refuses to trigger? Four typical reasons.
Signed up with Google but try email/password (or vice versa) — ChatGPT silently refuses and looks like a wrong password.
Download button returns nothing or a 0-byte file — typically render state or browser blocker.
Claude's Chrome extension shows attached but the page isn't in context? Permission, page type, or active tab.
You wanted execution; agent stopped every 30 seconds with "should I use TypeScript?" Define defaults in CLAUDE.md + an explicit "only ask for destructive ops" rule.
Agent suddenly forgets earlier answers, re-reads CLAUDE.md, contradicts the plan. Auto-summarization dropped the load-bearing details. Re-anchor or restart.
Claude Code keeps re-reading the same files or misses other dirs entirely? Anchor with CLAUDE.md and tighten working dir.
You fed a detailed audit and Claude Code did its own thing. The report is context, not a contract — convert to a numbered checklist, execute one item at a time.
Agent suggests "extract this into a microservice" when you're intentionally monolithic. Codify conventions in CLAUDE.md + do/don't examples from real files.
The diff is polished code — for the wrong feature. Force a restate-before-execute step; misalignment almost always happens at the plan stage, not the code stage.
You approved a 5-step plan; Claude did 7 steps, skipped one, and refactored adjacent code. Bind execution to the approved plan + post-step status updates.
Uncommitted edits gone after agent ran. Local-history recovery, then enforce "commit before agent" + dirty-state checks.
Claude Code editing the wrong files, duplicating existing functions, missing key files? It's almost never the model — it's missing project context. Seven ways to make Claude Code actually read your codebase.
You asked for a small change, got a 5-file diff. Set a hard editable-file list in the prompt + use `FOLLOWUPS.md` to capture adjacent issues without fixing them.
Halfway through a refactor, Claude Code says you hit a limit. Identify which limit (5-hour / weekly / per-model), save state, pick the right resumption path.
Agent did 60% then went silent — no error, no completion. Three flavors: context exhaustion, tool hang, silent abort. Each has its own diagnosis.
Agent repeats the same edit, oscillates between two states, or chases a flaky test forever. Six loop signatures and the one-prompt fix for each.
Modified a file you didn't intend — usually similar names, or it followed an import chain. Git-revert, then re-scope with allow/deny lists in the prompt.
A connector refuses to authorize or returns zero data. Three locks: workspace admin policy, OAuth scope, target-app policy.
File generation in Claude bills heavier than chat — here is how it counts and how to conserve.
GitHub connector refuses to connect or shows zero repos? Three layers usually fail: OAuth scope, org permission, repo visibility.
When Claude gives confidently wrong answers, the fix is rarely "switch model." Context, system prompt, and retrieval matter more.
After 50+ turns Claude starts contradicting itself or forgetting recent decisions. Here is what is happening and how to reset.
Claude keeps retrying and looping on rate-limit errors — the fix is back-off, batch, and conversation hygiene.
A previously-working tool greys out — workspace admin policy, plan, or temporary outage.
You asked Codex for an audit; got a 50-bullet report mixing typos with architecture. Re-scope by dimension, cap output size, force file:line.
Codex stops mid-patch — broken imports, half-converted types, untouched call sites. Bind "done" to a verifier, not a vibe.
Codex creates `utils.v2.ts` next to `utils.ts` instead of editing in place. Force in-place edits with explicit AGENTS.md rules + git as the safety net.
Codex skips the build, misreads the output, or trusts a truncated tail. Use machine-readable verifiers + exit codes, not prose summaries.
The reported bug is gone, two adjacent features regressed. Cap blast radius, enumerate call sites, prefer caller-side guards over shared-util changes.
New files land in `/src/` when your repo uses `/app/`; deps go to the root `package.json` in a monorepo; tests use a framework you don't have. Fix with AGENTS.md + canonical-example pointers.
Codex confidently uses a column that doesn't exist, an env var with the wrong shape, or a function signature it never read. Force quote-before-write grounding.
Codex uses `getUserById` when your codebase uses `findUserById`. Codify each convention as `rule + canonical example` in AGENTS.md.
"Patch hunk failed to apply" — file moved between Codex's read and write. Refresh state, normalize whitespace, or split the patch.
"Consider error handling" / "add tests" — bullets that work on any PR. Fix with specific review questions tied to file:line.
Functionally correct but reads like a stranger wrote it — async/await mixed with .then(), wrong import ordering, comment style off. Anchor to a canonical file + enforce with lint.
"Test happy path and error path" — useless in 2026. Force tests bound to the function's actual signature, edge cases, and bug history.
Codex creates files in the wrong place or with wrong conventions — constrain with AGENTS.md and explicit refs.
EU / UK / California users need consent UI. Bare minimum for compliance.
Browser blocks request with CORS error — server config or wrong origin.
You hit Apply, Cursor says it's done, but the file never changed — usually a stale snapshot, an outside edit, or a locked file.
Cursor shows edits but Apply does nothing or fails silently.
Composer is great in a small repo and loses the thread in a 50k-file monorepo. Force focus with explicit context, not heroic indexing.
Composer rewrote 10+ files and broke working code — prompt was too open and the agent had too much default scope.
Open a team repo and Cursor's formatting / AI behavior changes — the repo's .vscode/settings.json overrode your user settings.
The context panel doesn't show the file you expected — retrieval scored low, the file is ignored, or it's too new to be indexed.
Composer hands you a 30-file / 2000-line diff and you can't review it honestly — splitting it into smaller PRs is the only safe move.
AI wrote a new formatDate but src/utils already has one — existing helpers weren't in retrieval; make them findable.
Editor shows old content after an AI edit, or save says "file modified externally" — watcher / AI write race.
Composer says done and touched files lint clean, but npm build fails — classic signature drift, missing import, or stale codegen.
Index spinner runs for hours with no progress — usually a huge repo, wrong ignore config, symlink loops, or permission failures.
Cursor edits only what it can "see" — fix by adjusting indexing scope and explicit @file references.
You @ one file and Cursor answers about a different same-named file — ambiguity, stale index, or symlink confusion.
Cursor pulls in old / vendored / generated files into context. Fix the index and ignore lists.
Tab and Composer use different naming / formatting / patterns than your repo — training prior beats retrieval; anchor explicitly.
Grey inline completions vanished — Tab toggled off, sign-in expired, Copilot stealing the key, or current file is too large / unsupported.
Agent runs a shell command and gets confused — wrong working dir, wrong package manager, env not loaded, or output truncated.
SSL pending for hours after domain hookup — usually DNS or CAA.
Vercel / Firebase says deploy ok, but visitors see yesterday's version.
You updated DNS records but the site shows old IP or fails to load.
You changed DNS and some users see new, some see old. Here's why and how to test.
Edge function exceeds the time limit on Vercel / Cloudflare / Netlify.
Works locally, fails prod — env var not set, or prefix issue (PUBLIC_ / VITE_ / NEXT_PUBLIC_).
Firebase deploy fails with permission errors — IAM, login, or project mismatch.
Calling a function returns "not found." Likely region, name, or deploy.
Hosting deploy fails — CLI version, quota, or firebase.json config.
After deploying to Firebase Hosting, the homepage works but /about and other subpages return 404? Your firebase.json rewrites are misconfigured. Fixes for SPA, SSG, static multipage, Astro, and Next.js.
You configured rewrites for SPA / functions but they don't trigger.
Tap-and-hold power doesn't bring up Gemini on Android — toggle, app version, region.
Same account, different chat lists across surfaces — Workspace, region, and pinned device profiles explain most of it.
Deep Research output is shallow or one-sided — usually scope, sources, and prompting.
Summaries miss key points or feel generic — anchor on outline, structure, and explicit asks.
Share or export menu missing, or shared link 404s. Workspace policy and account tier.
File attached but Gemini "doesn't see" it, or summary is wildly off? Size, type, and Drive permission.
"Permission denied" or "Cannot access your account" when Gemini tries Gmail / Calendar.
Image generation in Gemini disabled or rejects your prompt — region, account type, or safety filter.
Gemini spins forever or returns nothing? Account, region, network, and Workspace gating are the usual suspects.
You hit a wall: "Try again later" or "Feature not available." This is usually quota or tier — not an outage.
Gemini side panel missing from Docs / Gmail? Three switches: domain, license, app.
You ask in Chinese, Gemini answers in English (or vice versa) — interface locale and explicit prompt language usually fix it.
You committed over what you wanted to keep. Three paths back. Usual causes: accidental commit overwrite; hard reset moved head. Start with: `git log -p -- <file>` to see the file's history.
Google replaced your title tag with a shorter / different one in search results.
Decoding the hreflang errors shown specifically in Google Search Console's International Targeting report — return tag missing, language code invalid, and how to act on each.
A 200-line AI diff isn't safe just because it compiles. Read it in the right order.
Works locally, breaks on Vercel or Render. Diff env vars, runtime version, filesystem case-sensitivity, network, and build process — the systematic checklist.
You write a 500-word 'super prompt' and get worse output than a 100-word one. This is the LLM length paradox.
Search results show a Google-generated snippet instead of your meta description.
Claude Code + Codex (or two parallel sessions) edit the same function differently and produce a conflict. Isolate scopes with worktrees; never let an agent resolve.
Two agents (Cursor + Claude Code) edited the same file. Merge cleanly, don't panic.
You changed something at the DNS provider and now email stopped working.
Sharing a page on Twitter / LinkedIn / Slack shows no preview image.
Share to LinkedIn / X / Slack and no image shows — meta tag, image size, or cache.
Stripe, Twilio, SendGrid all return 429 once traffic ramps. Read Retry-After, add exponential back-off, cache GETs, and batch writes — in that order.
You configured redirects but they don't fire — order, format, host quirks.
You changed robots.txt but Google still crawls / indexes the same URLs.
/rss.xml or /feed.xml 404 — endpoint missing, wrong filename, or host caching.
/sitemap.xml or /sitemap-index.xml returns 404 — integration off or `site` missing.
Submitted a sitemap to Search Console weeks ago and still no indexing — or only a few pages indexed? Sitemap submission ≠ indexing. Here are the six most common real reasons and their fixes.
You bound a custom domain on Vercel / Firebase / Netlify but SSL stays "pending."
Images and CSS 404 after deploy but work locally. Five typical causes — missing dist/ copy, base path, content hash, public folder, host upload step.
Browser shows nothing, no error — almost always hydration or JS import failure.
S3 / Firebase Storage / Supabase Storage upload 403s — IAM, signed URL, or bucket policy.
Rich Results Test shows your JSON-LD has warnings or invalid fields.
You configured a subdomain but it doesn't resolve to your site.
Suno Extend continues from the frequency at your cursor plus the style text — not the song's identity. The cut-point and style-consistency fixes that smooth the seam.
Sad lyrics with upbeat backing — fix by aligning style and tempo.
You wrote lyrics, Suno improvised. Structure tags + lyric mode help.
Song just stops or fades poorly. Tag the outro and describe how to end. Usual causes: no [outro] tag; length limit cut mid-phrase. Start with: add `[outro]` and describe: "fade out repeating hook.".
Suno default outputs are usually 1–2 minutes. There's a standard workflow to extend them into proper 3+ minute singles: Extend, Bridge, Final Chorus, Outro, Replace Section. Full steps and prompts.
Song doesn't build — no payoff at the chorus. Structure tags + dynamics.
Your "synthwave, retro, 80s synth" prompt produces a piano ballad. Why.
Suno repeats the chorus byte-for-byte unless you vary it. Break the loop at three layers — lyrics tweaks, melody hints, and structure tags.
Chinese / mixed-language lyrics get mangled syllables. Usual causes: model is english-biased; tone marks missing. Start with: spell out tones with pinyin if needed.
Vocals feel digital and stiff. Style + line length usually fix it.
You asked for lo-fi, got pop. Style descriptors are mis-ordered or vague.
Supabase URL or anon key undefined in prod — host env config or prefix mismatch.
Empty results despite data in the table. RLS policy too strict.
/foo redirects to /foo/ then to /foo (or 308 → 301 chain). Pick one and stick to it.
Site builds but 500s in production — usually serverless function, env vars, or edge runtime.
Build never finishes — typically OOM, dependency deadlock, or build timeout.
Provider says webhook delivered, your endpoint never sees it.
Apply too early, get rejected. Too late, miss revenue. The middle ground.
www.example.com works but example.com doesn't (or vice versa).
AI-generated faces come out warped, twisted, or melted? Usually it's not the prompt. Here's the 3-step fix path: tighten framing, raise resolution, then face restore.
ChatGPT shows a blank page, hangs on a spinner, or errors out? Work through this 5-step triage: region, DNS, proxy, Cloudflare challenge, OpenAI status.
ChatGPT login failures cluster into 3 buckets: email-password issues, Google SSO bounce, and suspicious activity warnings. Here's the shortest fix for each.
Claude says 'usage limit reached'? Here's how the limit actually counts (context + output, weighted by model), when it resets, and six effective ways to stretch it.
Search Console says 'Crawled — currently not indexed'? Google looked, but chose not to index. Here are the 5 most likely causes in order, and the shortest fix path.
Cursor stuck on Indexing? 90% of the time it's trying to index node_modules, dist, .next, or cache directories. Here's the .cursorignore template and a clean rebuild flow.
noindex blocks indexing. robots.txt blocks crawling. They are not the same. A short table for when to use which, and the most common mistake that breaks both.
Suno verse sounds fine but the chorus falls flat? The problem is always in the first 4 bars. Three levers that actually work: key, rhythmic density, hook landing.
When a Vercel deploy goes red, the log already tells you what's broken — if you know where to look. Three key positions, plus the five most common failure modes.
Your site has been live for a week and still nowhere on Google? Work through the 10 most common causes: robots, noindex, wrong canonicals, JS rendering, sandbox period, thin content.