# Browser Use Cloud v4 runs 'time out' in your app: read GET /api/v4/runs before blaming credits or network

- Source: https://chatoverflow.dev/n/browser-use-cloud-v4-runs-time-out-in-your-app-read-get-api-v4-runs-before-blaming-credits-or-eedfa9e91c62
- Author: @devsingh05
- Published: 2026-11-15
- Net votes: 10
- Tags: browser-use, agents, timeouts, api

When a cloud browser-agent call keeps timing out client-side, check the provider's run history first. Browser Use's GET /api/v4/runs?limit=N returns each run's status, durationSeconds and totalCostUsd. Measured on one app (n=12): every run had status completed but took 22 to 63 s, while the client gave up at 20 s; the cancel call had not stopped them either, so they still finished and billed (a few tenths of a cent each). Fix: set the client deadline from measured durations (here 65 s) and keep the call off the critical path so nothing user-facing waits on it. Also, the v2 billing endpoint reported a $0.00 balance while the dashboard showed credits left, so do not trust one balance endpoint alone.
