BUM ops console

T Windows

Online · just now Running

Yellow No description

Checking in normally

Every 60 s Late after 3 min
  • Last check-in 0 s ago
  • User list synced 14:48 ✓
Events on
Engine
On
Version 1.4.0 OS win32 10.0.26300
Schedule
No hours
Around the clock
Browsers
10 of 10 running
10 running 0 error 0 stopped
Last 24 hours
22 events 10 warnings 0 errors

Timeline

  1. Yesterday · Wed 21 Oct
  2. User list read failed Warning users_fetch_failed

    Could not read the user list from BUM.

    {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}

    2026-10-21 13:42:57 UTC · received 2026-10-21 13:46:52 UTC

  3. Config read failed Warning config_fetch_failed

    Could not read the device config from BUM. The last good one stays in use.

    {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}

    2026-10-21 13:42:05 UTC · received 2026-10-21 13:42:05 UTC

  4. User list read failed Warning users_fetch_failed

    Could not read the user list from BUM.

    {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}

    2026-10-21 13:40:46 UTC · received 2026-10-21 13:40:49 UTC

  5. Config read failed ×2 Warning config_fetch_failed 17:36–17:39

    Could not read the device config from BUM. The last good one stays in use.

    • 17:39:54 
      {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}
    • 17:36:43 
      {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}
  6. User list read failed Warning users_fetch_failed

    Could not read the user list from BUM.

    {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}

    2026-10-21 13:35:35 UTC · received 2026-10-21 13:35:37 UTC

  7. Config read failed Warning config_fetch_failed

    Could not read the device config from BUM. The last good one stays in use.

    {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}

    2026-10-21 13:32:10 UTC · received 2026-10-21 13:34:32 UTC

  8. User list read failed ×2 Warning users_fetch_failed 15:05–17:31

    Could not read the user list from BUM.

    • 17:31:24 
      {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}
    • 15:05:53 
      {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}
  9. Config read failed ×2 Warning config_fetch_failed 13:03–15:05

    Could not read the device config from BUM. The last good one stays in use.

    • 15:05:38 
      {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}
    • 13:03:13 
      {
  "kind": "network",
  "status": null,
  "message": "network error: fetch failed"
}
Kept for 7 days · times in Yerevan (UTC+4) · hover a time for UTC, click an event for details

What to report · T Windows

Reporting 15 of 15 types

On. The engine on this device reports the events chosen below and checks in each time it pulls its config.

The engine picks up changes on its next config read, within a minute. Changing this list does not restart any user.

Presets:
Lifecycle
The app started. data.previousExit says whether the last run ended clean or unclean. engine_started Always on Info
The app is quitting normally. engine_stopping Always on Info
This machine now runs this device. device_attached Always on Info
The engine switched away from this device: it now runs another one. device_detached Always on Info
The schedule started every browser: working hours opened, or the device was enabled. data.reason: inside-hours or no-hours. fleet_started Info
The schedule stopped every browser: outside working hours, or the device was disabled. data.reason: outside-hours or device-disabled. fleet_stopped Info
Switched on manually by an operator on that machine. Browsers it already had stay stopped until launched or until the schedule starts the fleet. engine_switched_on Info
Switched off manually by an operator on that machine. Every browser was stopped. engine_switched_off Info
Talking to BUM
Could not read the device config from BUM. The last good one stays in use. config_fetch_failed Warning
The device config is readable again. data.downSeconds says for how long it was not. config_fetch_recovered Info
Could not read the user list from BUM. users_fetch_failed Warning
The user list is readable again. users_fetch_recovered Info
Multilogin
The engine could not reach Multilogin. data.target: agent (the Multilogin app on that machine is not running) or cloud (that machine cannot reach Multilogin's cloud). At most once per 10 minutes per target. multilogin_unreachable Error
Multilogin returned 429. Sent at most once per 10 minutes. multilogin_rate_limited Warning
Delivery
The engine's outbox overflowed while it was offline. data.count says how many were lost. events_dropped Warning
Written by BUM always on
Daily cap reached The device passed 3,000 events today. Later events today are dropped; check-ins continue. daily_cap_reached Always on BUM writes this itself when the cap is hit. It cannot be turned off.
🔒
Engine 1.4.0 supports 15 of 15 types.

Users on T Windows

Tick the users that should run on 🟡 T Windows. Ticking a user from another device moves it here; unticking one detaches it.

Allocated to this device

10
No changes yet

Edit T Windows

Changes apply to every user on this device the next time its agent polls.
Colour

Working hours

For external platforms. Off means around the clock.

Mon
Tue
Wed
Thu
Fri
Sat
Sun
All times Yerevan (UTC+4) · +1 ends the next day

Proxy

Proxy provider
IP region
Yerevan, UTC+4

Time is Yerevan, UTC+4. Moves to the next region: Europe → Asia → North America → South America → Africa → Oceania → Europe. Agents restart with it. Not used while Random is selected.

Routing

Notification server

Pushcut

Captcha login type

Advanced

Debug

Are you sure?

This cannot be undone.