Checking in normally
Every 60 s Late after 3 min- Last check-in 56 s ago
- User list synced 13:58 ✓
Timeline
- Today · Thu 22 Oct
-
Fleet started Info
fleet_startedThe schedule started every browser: working hours opened, or the device was enabled. data.reason: inside-hours or no-hours.
{ "reason": "no-hours" } -
Fleet stopped Info
fleet_stoppedThe schedule stopped every browser: outside working hours, or the device was disabled. data.reason: outside-hours or device-disabled.
{ "reason": "device-disabled" } - Yesterday · Wed 21 Oct
-
User list read recovered Info
users_fetch_recoveredThe user list is readable again.
{ "downSeconds": 353 } -
Config read recovered Info
config_fetch_recoveredThe device config is readable again. data.downSeconds says for how long it was not.
{ "downSeconds": 132 } -
Config read failed Warning
config_fetch_failedCould not read the device config from BUM. The last good one stays in use.
{ "kind": "timeout", "status": null, "message": "API request timed out after 15000ms" } -
Config read recovered Info
config_fetch_recoveredThe device config is readable again. data.downSeconds says for how long it was not.
{ "downSeconds": 64 } -
Config read failed Warning
config_fetch_failedCould not read the device config from BUM. The last good one stays in use.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
User list read failed Warning
users_fetch_failedCould not read the user list from BUM.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
Config read recovered Info
config_fetch_recoveredThe device config is readable again. data.downSeconds says for how long it was not.
{ "downSeconds": 60 } -
Config read failed Warning
config_fetch_failedCould not read the device config from BUM. The last good one stays in use.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
User list read recovered Info
users_fetch_recoveredThe user list is readable again.
{ "downSeconds": 71 } -
Config read recovered Info
config_fetch_recoveredThe device config is readable again. data.downSeconds says for how long it was not.
{ "downSeconds": 131 } -
User list read failed Warning
users_fetch_failedCould not read the user list from BUM.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
Config read failed Warning
config_fetch_failedCould not read the device config from BUM. The last good one stays in use.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
User list read recovered Info
users_fetch_recoveredThe user list is readable again.
{ "downSeconds": 71 } -
Config read recovered Info
config_fetch_recoveredThe device config is readable again. data.downSeconds says for how long it was not.
{ "downSeconds": 60 } -
User list read failed Warning
users_fetch_failedCould not read the user list from BUM.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
Config read failed Warning
config_fetch_failedCould not read the device config from BUM. The last good one stays in use.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
User list read recovered Info
users_fetch_recoveredThe user list is readable again.
{ "downSeconds": 3301 } -
Config read recovered Info
config_fetch_recoveredThe device config is readable again. data.downSeconds says for how long it was not.
{ "downSeconds": 3301 } -
User list read failed Warning
users_fetch_failedCould not read the user list from BUM.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
Config read failed Warning
config_fetch_failedCould not read the device config from BUM. The last good one stays in use.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
Fleet started Info
fleet_startedThe schedule started every browser: working hours opened, or the device was enabled. data.reason: inside-hours or no-hours.
{ "reason": "no-hours" } - Mon 19 Oct
-
Config read recovered Info
config_fetch_recoveredThe device config is readable again. data.downSeconds says for how long it was not.
{ "downSeconds": 60 } -
Config read failed Warning
config_fetch_failedCould not read the device config from BUM. The last good one stays in use.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } -
Config read recovered Info
config_fetch_recoveredThe device config is readable again. data.downSeconds says for how long it was not.
{ "downSeconds": 60 } -
Config read failed Warning
config_fetch_failedCould not read the device config from BUM. The last good one stays in use.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } - Sat 17 Oct
-
Config read recovered Info
config_fetch_recoveredThe device config is readable again. data.downSeconds says for how long it was not.
{ "downSeconds": 60 } -
Config read failed Warning
config_fetch_failedCould not read the device config from BUM. The last good one stays in use.
{ "kind": "network", "status": null, "message": "network error: fetch failed" } - Thu 15 Oct
-
Device attached Info
device_attachedThis machine now runs this device.
{} -
Engine started Info
engine_startedThe app started. data.previousExit says whether the last run ended clean or unclean.
{ "os": "darwin 13.7.8", "version": "1.2.1", "previousExit": "clean" }