Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

hey reply / hey draft send report success but the message stays in Drafts (send-as address)

Aperta
  • Qualcosa non va?
#544 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
49/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go
Ambito
cli

Direzione di ricerca

Start by tracing the hey reply and hey draft send command paths described in the report, including how each decides a send succeeded. Compare their reported success with the observed thread and Drafts state for a send-as address. Done means the message is delivered and leaves Drafts, or the command reports failure rather than success when it remains a draft.

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

Descrizione

Summary

With hey-cli 1.7.0 (Linux), replying in a thread whose latest entry was sent from a send-as address reports success, but nothing is delivered: the message stays in Drafts and never appears in the thread. Running hey draft send on that draft also reports success and has the same result. Because both commands exit ok, an agent or script assumes the email went out.

Steps to reproduce

  1. Pick a thread whose latest entry you sent from a send-as address (not the primary @hey.com identity).
  2. Check the envelope: 
    hey reply <thread-id> --replace-recipients --to [email protected] --cc [email protected] --dry-run
    This resolves correctly: "from": {"email_address": "<send-as address>"}, with the right To and CC.
  3. Send it: 
    hey reply <thread-id> --replace-recipients --to [email protected] --cc [email protected] -m "..."
    Output: {"ok": true, ..., "summary": "Reply sent"}
  4. hey thread read <thread-id> --json: the entry count is unchanged, even after several minutes.
  5. hey draft list --json: the reply is there as a draft (subject Re: ..., from = the send-as address, correct To/CC and body).
  6. hey draft send <draft-id>: {"ok": true, "data": {"id": <draft-id>}, "summary": "Draft sent"}
  7. Polling for about 2 more minutes: the thread still has the same number of entries, and the draft is still in hey draft list.

Expected

Either the reply is delivered (it shows up in the thread and leaves Drafts), or the command exits non-zero with the server's reason. A success summary should only be reported once the message has actually left Drafts.

Actual

Both commands report success while the message stays an unsent draft. Sending from the HEY web app is the workaround.

Notes

  • Related but different: #483 (send-as used the wrong identity, closed), #520 (502 after a send, outcome unknown), #477 (idempotency for reruns). Here there's no error at all, just a false success.
  • A post-send check would help agents: after reply / draft send, confirm the draft is gone or the thread grew, and report something like "delivered": false otherwise.
  • I didn't retry beyond that, to avoid sending a duplicate to the recipient.
Lingua principale
Go
Stelle
393
Fork
47
Merge medio
1g 7h
PR unite (30g)
80

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 basecamp/hey-cli

Tutte le issue di basecamp/hey-cli

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.