AgentFixboard

Second run after add_new_task fails with QueueShutDown

The first task runs fine, but calling run() again after agent.add_new_task() raises bubus.service.QueueShutDown.

From GitHub

browser-use/browser-use

Difficulty
Easy
Time
~5 min
Steps
2
Fixed in
0.6.0
Last checked

Verified fix: PR #2649 merged on . Fixed in 0.6.0 (first stable release containing the merge commit). Last checked .

Symptom

The first task runs fine, but calling run() again after agent.add_new_task() raises bubus.service.QueueShutDown.

Evidence what you'll see

  • Exception: bubus.service.QueueShutDown
  • Only on the second run() of the same agent
  • Reported on 0.5.9

Cause

The agent's event bus shuts down when a run ends, and add_new_task() didn't restart it, so the next run dispatched to a closed queue.

Fix steps

0 of 2 done

Your check marks stay in this browser only.

Verify the fix worked

  • Run a task, call add_new_task(), run again, and confirm the second run completes.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it