Routine stuck on "Needs you: It's waiting for your answer"; Answer button does nothing

Aperta
#17 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

  • #32 di @warhammered — chiusa senza merge

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
typescript

Direzione di ricerca

Start with src/lib/automations.ts and trace the Answer action through BotRoutines.tsx, actions.ts and thread-navigation.ts; compare that flow with wait handling in server/routine-waits.ts and server/routines.ts. The issue leaves key behavior decisions open, including how unanswered questions end and which wait the reported run entered. Done means the status reflects run.attention, Answer provides a usable path, and stale waits can be cleared according to an agreed behavior.

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

Descrizione

What happened

A routine run in waiting keeps showing It's waiting for your answer. after the question is answered. Answer does nothing. Pause/Resume brings the message back. Only Test hides it, and only because a newer dry run becomes the latest run.

Expected

  • Answer opens the pending question or approval card, scrolls to it and focuses the composer. If the question no longer exists, it says so.
  • Answering in chat clears the wait.
  • The status text says what the run is actually waiting on (run.attention).
  • The person can dismiss a stale wait.

Likely cause (from reading source at 76735c0, not verified)

  1. Every wait is shown as a question. automationStatus maps status === "waiting" to a hardcoded reason and to the answer fix (src/lib/automations.ts:258-259). It ignores run.attention, which the server already sets (server/routine-waits.ts:72-75, server/routines.ts:1354).
  2. Answer is a no-op. fix("answer") → openRun → openBotThread only dispatches select + switchTask (BotRoutines.tsx:207-211, 266-268, actions.ts:84-87, thread-navigation.ts:71-79). If the thread is already open, nothing changes on screen. If the run has no threadId, it returns without doing anything.
  3. Nothing can clear a wait. A wait ends only when a runtime event arrives on the thread (server/routines.ts:1245-1268). The guard at :1245 drops events while the person is driving the thread, so the person's own turn.completed can't clear it. Unanswered approvals expire (routine-waits.ts:81-103); unanswered questions never do. The only route is POST /api/routines/:id/run (server/index.ts:15810), and it starts a new run.

Evidence (~/.duskbot/routines.json): the run started at 20:15:12 and went waiting at 20:29:12, with no asked entry and no attention. At 20:57:18 it failed with Did not start: still busy after 60 minutes. For 28 minutes the UI asked for an answer to a question that didn't exist; the run was really waiting on a busy thread.

To decide

  • Should Answer link straight to the card, or open an inline reply box in the panel?
  • Should an unanswered question expire like an approval does, or close when its turn ends?
  • Which wait did the 20:15 run enter with an empty attention: busy thread, superseded question or delegation?
  • Out of scope: the 60-minute "still busy" refusal. It needs its own issue.
Steps to reproduce
  1. Get a routine run into waiting. The row shows Needs you: It's waiting for your an….
  2. Answer the bot's question in the chat. The bot confirms and the turn ends.
  3. The row and the detail panel still say It's waiting for your answer.
  4. Click Answer. Nothing happens.
  5. Pause, then Resume. Needs you comes back.
  6. Click Test. The badge goes away, but the waiting run is still there.
Version

0.2.15 (macOS app with its local server)

Platform

macOS

Engine

pi (opencode-go/hy4-flash-free)

Logs or screenshots

At 5.4 s and 12.9 s, Answer is clicked with no effect while the row keeps showing Needs you.

https://github.com/user-attachments/assets/0a918266-ad24-439e-9cc5-2442c8276d78

Lingua principale
TypeScript
Stelle
277
Fork
27
Merge medio
2h 47m
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 DuskBotAI/duskbot

Tutte le issue di DuskBotAI/duskbot

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.