I claimed done_ids() was binning rate-limited tasks forever. It wasn't:
/task-completed has always refused to persist 'ratelimited' and 'requeue'
rows (they stay PENDING by design), so such an id can never reach
results.jsonl. Verified against the copy that was actually running.
The done_ids() guard stays as defence in depth against a hand-appended row,
but its comment no longer claims to fix a bug that didn't exist. The real
bug in that commit — no circuit breaker on a failure streak — stands, as
does the actual root cause in 82d5ff4 (promptEchoed matched a 60-char prefix).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Two bugs, both found by autopsy of the djsim_phonewall run (2026-07-08):
15 calendar prompts queued, 2 generated, then THIRTEEN consecutive
"Timed out — no new asset" at a metronomic 3m30s apart. 45 minutes of the
driver politely feeding prompts into a Flow that had stopped generating.
1. NO CIRCUIT BREAKER. Each timeout threw, was reported failed, and the
loop moved straight on. When Flow goes quiet it does not spontaneously
start again. Now: 3 consecutive failures -> clear isRunning, log a loud
system message, leave the queue intact for a hand-resume. (The abuse-flag
path already had consecutiveRateLimits; failures had nothing.)
2. done_ids() COUNTED 'ratelimited' AS DONE. handleRateLimit() writes that
status with the explicit comment "report the task back as pending" — and
the server then binned the task forever. Now excluded. 'failed' is still
counted: a timeout may have burned credits invisibly, so nothing retries
automatically.
requeue.py: the deliberate way to retry. --list / --dry / by id or prefix /
--failed. Writes a .bak, never re-runs a success. Used it to make the 13
cal79 prompts pending again.
Note for whoever reads this next: the LIVE server + queue live in
~/Library/Application Support/flowrinse/, not this repo. HERE is derived
from the script's own dir, so running the repo copy silently serves the
stale Jul-6 queue. Copy the script over, run it from there.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- waitForAgentReady: after (re)load, wait for the sidebar to hydrate before typing
- post-submit success check = square stop button (or emptied box); no square after
Enter + submit fallback -> hard refresh (bypassCache via background) and requeue
- 'Something went wrong' surviving Try-again -> hard refresh + requeue (was: fail)
- requeue attempts capped at 3 per task (chrome.storage, survives reloads)
- server: 'requeue' status keeps task pending; INFLIGHT entries expire after 15 min
so a reloaded tab gets its task re-served
- banks/djsim_batch3.jsonl: 18-task 90sDJsim asset bank (queued live)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
DOM automation for Google Labs Flow — background worker injects trusted input
via the DevTools Protocol (Flow's editor ignores synthetic events), polls a local
queue, harvests generated asset URLs. Includes the generated game+promo prompt bank.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
