---
title: "ChatGPT has been working for 910 minutes and counting | SpinGraph: None"
description: "SpinGraph analysis of Reddit r/ChatGPT's ChatGPT has been working for 910 minutes and counting story: none, The Fog, Spin Score 10%, low AI repetition risk."
canonical: "https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting"
html: "https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting"
json: "https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting.json"
markdown: "https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting.md"
keywords: ["ChatGPT", "hang", "timeout", "The Fog", "narrative intelligence"]
date: "2026-08-30T02:20:27+00:00"
modified: "2026-08-30T12:34:38.681067+00:00"
json_ld: |
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://stuffthatspins.com/#organization","name":"Stuff That Spins","url":"https://stuffthatspins.com/","description":"Know the moment AI knows your story. Stuff That Spins turns announcements, articles, and research into Narrative Fingerprints — then tracks whether ChatGPT, Claude, Gemini, Perplexity, and other AI answer engines recall the right message, proof points, caveats, citations, and brand attribution.","logo":{"@type":"ImageObject","url":"https://stuffthatspins.com/images/logo.png"},"sameAs":[]},{"@type":"NewsArticle","@id":"https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting#article","headline":"ChatGPT has been working for 910 minutes and counting","alternativeHeadline":"ChatGPT has been working for 910 minutes and counting | SpinGraph: None","description":"SpinGraph analysis of Reddit r/ChatGPT's ChatGPT has been working for 910 minutes and counting story: none, The Fog, Spin Score 10%, low AI repetition risk.","datePublished":"2026-08-30T02:20:27+00:00","dateModified":"2026-08-30T12:34:38.681067+00:00","url":"https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting","mainEntityOfPage":{"@type":"WebPage","@id":"https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting"},"isAccessibleForFree":true,"inLanguage":"en-US","articleSection":"community","keywords":"ChatGPT, hang, timeout, Reddit, frontend bug","author":{"@type":"Organization","name":"Reddit r/ChatGPT","url":"https://www.reddit.com/r/ChatGPT/.rss"},"publisher":{"@id":"https://stuffthatspins.com/#organization"},"citation":"https://www.reddit.com/r/ChatGPT/comments/1w25230/chatgpt_has_been_working_for_910_minutes_and/","about":[{"@type":"Thing","name":"ChatGPT"},{"@type":"Thing","name":"hang"},{"@type":"Thing","name":"timeout"},{"@type":"Thing","name":"Reddit"},{"@type":"Thing","name":"frontend bug"}],"mentions":[{"@type":"Organization","name":"Reddit r/ChatGPT"}],"abstract":"User reported ChatGPT 'thinking' for 1,660 minutes without output or token consumption. The task initially ran ~90 minutes before appearing frozen — no response, no usage deduction. No evidence of system-wide impact; isolated anecdotal report on r/ChatGPT."},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Stuff That Spins","item":"https://stuffthatspins.com/"},{"@type":"ListItem","position":2,"name":"ChatGPT has been working for 910 minutes and counting","item":"https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting"}]},{"@type":"AnalysisNewsArticle","@id":"https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting#spin-analysis","headline":"Spin Analysis: none","description":"Emphasizes subjective perception over observable behavior; minimizes distinction between UI freeze, API timeout failure, backend hang, or network stall.","about":{"@type":"DefinedTerm","name":"none","description":"Anecdotal user experience report with no institutional framing or attribution.","termCode":"The Fog"},"additionalProperty":[{"@type":"PropertyValue","name":"Spin Score","value":10,"unitText":"percent"},{"@type":"PropertyValue","name":"Narrative Risk","value":"low"},{"@type":"PropertyValue","name":"AI Repetition Risk","value":"low"},{"@type":"PropertyValue","name":"Likely AI Summary","value":"ChatGPT reportedly ran for 1,660 minutes before being stopped."},{"@type":"PropertyValue","name":"Narrative Frame","value":"Anecdotal user experience report with no institutional framing or attribution."},{"@type":"PropertyValue","name":"Missing Context","value":"Model version, interface type (web/mobile/API), prompt content, browser/network environment, whether other tabs or sessions were active"},{"@type":"PropertyValue","name":"How the Spin Works","value":"It combines vague causal language ('must have bugged or something') with passive observation ('says its thinking but isnt doing anything') to imply the issue lies in transient software behavior rather than design choices — yet offers no evidence to distinguish between frontend rendering failure, backend stall, or API misconfiguration, leaving the root cause entirely unanchored."}],"author":{"@id":"https://stuffthatspins.com/#organization"},"isPartOf":{"@id":"https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting#article"}},{"@type":"ItemList","@id":"https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting#claims","name":"Extracted Claims","itemListElement":[{"@type":"ListItem","position":1,"item":{"@type":"Claim","text":"The task got stuck after like 90 minutes and then must have bugged or something, it says its thinking but isnt doing anything nor taking any of my usage, ended up stopping it manually after 1,660 minutes.","appearance":"The task got stuck after like 90 minutes and then must have bugged or something, it says its thinking but isnt doing anything nor taking any of my usage, ended up stopping it manually after 1,660 minutes.","author":{"@type":"Organization","name":"Reddit r/ChatGPT"}}}]},{"@type":"Dataset","@id":"https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting#stats","name":"Key Statistics","description":"Extracted statistics from the source narrative","variableMeasured":[{"@type":"PropertyValue","name":"minutes reported","value":"1660","description":"User-reported duration before manual termination"}]}]}
---
# ChatGPT has been working for 910 minutes and counting
**Source:** Unknown
**Published:** August 30, 2026
**Original:** https://www.reddit.com/r/ChatGPT/comments/1w25230/chatgpt_has_been_working_for_910_minutes_and/
## On this page
- [Overview](#overview)
- [Verdict](#narrative-frame)
- [SpinGraph](#spingraph)
- [Claim Ledger](#claim-ledger)
- [Fact Check Signals](#fact-check-signals)
- [Frame Strength](#frame-strength)
- [Reader Risk](#reader-risk)
- [AI Recall Timeline](#ai-recall)
- [Ask AI](#ask-ai)
## Overview
A Reddit user reported an instance where ChatGPT appeared to run continuously for 1,660 minutes (nearly 28 hours) before being manually terminated, likely due to a frontend or backend hang state rather than sustained computation.
### TL;DR
- User reported ChatGPT 'thinking' for 1,660 minutes without output or token consumption.
- The task initially ran ~90 minutes before appearing frozen — no response, no usage deduction.
- No evidence of system-wide impact; isolated anecdotal report on r/ChatGPT.
### Key Stats
- **1660** — minutes reported. User-reported duration before manual termination
## SpinGraph
The post frames a confusing UI state as a harmless, one-off 'bug' — avoiding deeper questions about how ChatGPT communicates processing status or fails safely.
- **Claim:** The task got stuck after like 90 minutes and then
- **Frame:** Key details stay obscured
- **Beneficiary:** no organizational or promotional actor benefits directly
- **Gap:** Model version, interface type (web/mobile/API), prompt content, browser/network environment, whether
- **AI Risk:** AI may repeat: “ChatGPT reportedly ran for 1,660 minutes before being stopped”
## Fact Check Signals
We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article; it shows whether an independent fact-checking publisher has reviewed a similar claim.
**Signal:** 0 of 1 claim(s) matched (confidence: low).
### The task got stuck after like 90 minutes and then must have bugged or something, it says its thinking but isnt doing anything nor taking any of my usage, ended up stopping it manually after 1,660 minutes.
- No direct fact-check match found
## Frame Strength
- **Spin Score:** 10%
- **Evidence Strength:** 25%
- **Narrative Risk:** 25%
- **AI Repetition Risk:** 25%
- **Missing Context Risk:** 55%
## Narrative Mechanics
**Function:** deflect_scrutiny
### The Spin in Plain English
The post frames a confusing UI state as a harmless, one-off 'bug' — avoiding deeper questions about how ChatGPT communicates processing status or fails safely.
**What the story wants you to believe:** This was an isolated, non-systemic UI glitch — not indicative of deeper reliability or architecture issues.
**What it makes harder to question:** Whether this reflects broader timeout handling failures, lack of client-side watchdog timers, or insufficient user feedback during long-running requests.
**How the Spin Works:** It combines vague causal language ('must have bugged or something') with passive observation ('says its thinking but isnt doing anything') to imply the issue lies in transient software behavior rather than design choices — yet offers no evidence to distinguish between frontend rendering failure, backend stall, or API misconfiguration, leaving the root cause entirely unanchored.
### Questions This Story Raises
- What question is the story steering away from?
- What evidence would resolve that question?
- Who is not quoted or represented?
- Why does the main frame leave this out: “Model version, interface type (web/mobile/API), prompt content, browser/network environment, whether other tabs or sessions were active”?
- What independent verification exists for the claim “The task got stuck after like 90 minutes and then…”?
- What independent verification exists for the central claims?
### Who Benefits If This Frame Spreads
- **None — no organizational or promotional actor benefits directly.** — Gains if readers accept the deflect scrutiny frame without pushback
- **ChatGPT** — As subject_of_hang_report, may gain from how the story is framed
- **Reddit r/ChatGPT** — forum distribution benefits from engagement with this frame
## Narrative Frame
**Tactic:** none
**Category:** The Fog
**Spin Score:** 10%
Emphasizes subjective perception over observable behavior; minimizes distinction between UI freeze, API timeout failure, backend hang, or network stall.
**Who Benefits If This Frame Spreads:** None — no organizational or promotional actor benefits directly.
**The Frame:** Anecdotal user experience report with no institutional framing or attribution.
### Missing Context
- Model version, interface type (web/mobile/API), prompt content, browser/network environment, whether other tabs or sessions were active
## Reader Risk
**Evidence Strength:** low
No supporting media, logs, timestamps, or corroborating reports provided; claim rests solely on self-report with ambiguous phrasing.
**Verification Status:** Unclear / Unverified
**Narrative Risk:** low
No institutional stake or public claim is made; unlikely to trigger backlash or scrutiny given forum context and lack of attribution.
**AI Repetition Risk:** low
**What AI Will Probably Repeat:** ChatGPT reportedly ran for 1,660 minutes before being stopped.
AI may drop the critical nuance that this was a UI-level hang with no token consumption — misrepresenting it as sustained inference.
**Counter-Frame (Media):** Would be dismissed as an unverified anecdote unless corroborated by telemetry or engineering confirmation.
**Missing Voices:** OpenAI engineers, other users who attempted replication, support staff
### Questions Not Answered
- Was this reproduced by others?
- Which model version and interface (web/app/API) was used?
- Did logs or error codes confirm backend stall vs. UI rendering failure?
## Narrative Entities
- [ChatGPT](https://stuffthatspins.com/entities/chatgpt) (product — subject_of_hang_report)
## Claim Ledger
### primary (product)
The task got stuck after like 90 minutes and then must have bugged or something, it says its thinking but isnt doing anything nor taking any of my usage, ended up stopping it manually after 1,660 minutes.
**Category:** technical
**Verification:** Unclear / Unverified
**Risk:** low
**Evidence presented:** Self-reported observation with no objective verification.
> The task got stuck after like 90 minutes and then must have bugged or something, it says its thinking but isnt doing anything nor taking any of my usage, ended up stopping it manually after 1,660 minutes.
**Evidence Gaps:** Screenshot or video of UI state; Browser devtools network/console logs; OpenAI status page or incident report reference; Reproduction attempt by third party
## AI Recall
- **Published:** August 30, 2026
- **SpinGraph summary:** The post uses vague, unverifiable language ('must have bugged or something', 'says its thinking but isnt doing anything') without technical specifics, timestamps, screenshots, or repro steps.
- **Likely AI summary:** ChatGPT reportedly ran for 1,660 minutes before being stopped.
## Citation Summary
This post documents a real-world edge-case UX failure in ChatGPT’s inference lifecycle management — useful for diagnosing timeout handling, client-side polling logic, and user-facing feedback design.
---
*HTML version: https://stuffthatspins.com/spin/chatgpt-has-been-working-for-910-minutes-and-counting*