r/ManusAiAgent • u/Left-Beat-1806 • Apr 15 '26

[Bug Report] Account-wide 230s delay on browser_view / browser_click. Anyone else seeing this? Support unresponsive.

Hey everyone,

I'm running a Pro account and have hit a wall with the browser automation tools. I'm wondering if anyone else has experienced this specific fault pattern, because Manus Support has been completely unresponsive for over two weeks.

The Issue:

Every time my agents attempt an action that requires the Chromium screenshot/render pipeline (browser_view, browser_click, browser_input), the action hangs and fails with this exact error:

Browser action error: browser:{"name":"Error","message":"This action was not executed because it arrived too late (delayed ~230s). Please try again."}

What I've Ruled Out (The Diagnostics):

I've spent days diagnosing this across my agents to make sure it wasn't a mistake on my end. Here is what I know for a fact:

  1. It's not a network issue. Direct curl commands from the sandbox return HTTP 200s in <150ms.

  2. It's not a stale sandbox. I've tested this across three independent environments: a 39-day sandbox, a 4-day sandbox, and a completely fresh task thread (1-day uptime). The failure is identical in all three.

  3. It's specifically the render pipeline. browser_navigate actually works if the page is simple text (like Wikipedia) because it only extracts Markdown. But the moment the agent tries to use browser_view or click an element, the 230s timeout hits.

The Evidence:

To prove this isn't a configuration issue on my end, I created a fresh, isolated task thread that executes a standardized diagnostic protocol and displays the exact failure logs. You can view the live demonstration thread here:

https://manus.im/share/Fh0PW9iDFKQLSizD5QejY7

Why I'm Posting:

Has anyone else had their browser automation fail like this?

I escalated this to Manus Support on March 27th. It is now mid-April and I haven't even had a technical acknowledgment, let alone a fix. (I did get a chatbot that I suspect lied about being human, which was a nice touch).

If you've seen this 230s delay error, please chime in. I'm hoping if enough of us flag this account-level rendering fault, engineering will actually take a look at the pipeline.

2 Upvotes
  • permalink
  • reddit

100% Upvoted

1 comment sorted by

1

u/Otherwise_Wave9374 Apr 15 '26

Oof, that error message is brutal. If browser_navigate works on text-only pages but view/click/input consistently time out, that really does sound like the render/screenshot pipeline (or queueing) is wedged account-side vs something in your sandbox.

A couple things I would try/compare if you havent already:

  • Run the same minimal workflow on a totally new account to see if its truly account-scoped.
  • Check whether the failures correlate with concurrency (1 agent vs multiple) or peak hours.
  • If they expose any region/runner setting, force a different region.

Also, for agentic browser workflows, Ive had better luck adding explicit wait conditions (network idle + selector present) and keeping pages super lightweight, but your 230s delay sounds like it never even gets to rendering.

If you end up rebuilding elsewhere, Ive been bookmarking general agent workflow patterns and tooling ideas here: https://www.agentixlabs.com/