Dot cloud task control regression: readable tasks return UNKNOWN/NOT_FOUND on continuation; direct resume also fails

Aperta
  • Qualcosa non va?
#52,374 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Ambito
api, cloud

Direzione di ricerca

The payload names no source files, tests or entry points in this repository; the failures are backend errors (UNKNOWN, NOT_FOUND) from cloud_threads send_message and create, and the cause is unknown. Reproducing needs access to the Codex Cloud backend and the listed request IDs, which a newcomer does not have. Work on this with a maintainer before writing any patch.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

app-server bug codex-web dots

Summary

Observed October 8–9, 2026 (UTC), using ChatGPT web on macOS and iOS with saved Codex Cloud environments. Dot successfully coordinated an existing cloud task earlier, then lost the ability to continue it or create a replacement. Task reads and saved-environment listing still succeed. A newly user-created cloud task is readable, but dot messaging returns NOT_FOUND.

This is a cloud-task coordination report, not a local desktop executor or trading/data API connection issue. Exact client/backend builds are unknown.

Verified behavior

  • Earlier on October 8, dot follow-up messages were admitted and actual command execution, file processing, and remote saves succeeded.
  • Later, cloud_threads.send_message to that same task repeatedly returned AppServerBackendRequestError: Something went wrong, error_code: UNKNOWN.
  • cloud_threads.create with a catalog-returned saved cloud environment also returned UNKNOWN. Subsequent task-list checks showed no newly created delegated task.
  • cloud_threads.read and list_environments continued to succeed.
  • A direct user message appeared in the old task and its status changed to inProgress, but this alone did not verify command execution. The user subsequently saw Failed to resume chat. Something went wrong and stopped that task.
  • The user reset the environment and created a new cloud chat with explicit implementation authorization. Dot can read its exact user instructions and inProgress status, but send_message to that exact readable task returns CloudThreadNotFoundError, error_code: NOT_FOUND, error_data.type: cloud_thread_not_found.
  • A final messaging attempt at October 9, 02:32 UTC returned the same NOT_FOUND result.

Selected diagnostic request IDs

  • Existing-task continuation: wfr_01a11e49cba4774496e64774c751a535 (October 9, about 01:42 UTC)
  • New cloud-task creation: df158839-38e0-4bbc-bc1e-52a7d6a96c54 (about 01:10 UTC)
  • Post-reset continuation: cb6111de-914c-4ad2-8c66-e5f217786a4b (about 02:10 UTC)
  • User-visible resume error: b6ddd305-f88e-4f06-9fbc-55cd02c2c04b
  • Latest creation retry: 521de1a3-f07b-9cb6-9b6a-514c77751fac (about 02:21 UTC)

Recovery attempts and limits

Bounded retries, direct user continuation, an environment reset, and a new user-created chat did not restore dot messaging. No security settings, credentials, or permissions were changed by the assistant to bypass the failure. The cause is unknown. We have not established disk exhaustion, network geography, model choice, context length, or approval policy as the cause. A separate earlier upload-approval denial occurred, but it is not evidence that these server/routing errors share that cause.

Expected behavior and impact

Dot should be able to continue an authorized readable cloud task, or receive a specific actionable error. Failures have required repeated manual message relays and prevented reliable unattended work. Please provide a non-destructive recovery procedure that preserves existing workspaces and unpublished files, and identify whether the task is actually executing when history says inProgress.

Related reports

  • #50015: same UNKNOWN create/follow-up pattern with readable history
  • #50168: readable cloud task but NOT_FOUND write path
  • #51372: manual cloud creation works while dot creation/continuation fail

Please consolidate if this is a duplicate. The October 7 dot thread-creation incident is marked resolved; no connection to this occurrence is established.

Submitted with AI assistance at the affected user's request. Private task/environment IDs, repository names, paths, source data, credentials, and conversation contents are omitted. Request IDs are included for backend tracing only.

Lingua principale
Rust
Stelle
133k
Fork
21.1k
Merge medio
1m
PR unite (30g)
997

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openai/codex

Tutte le issue di openai/codex

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.