Skip to content

High-performance browser automation bridge and multi-instance orchestrator with advanced stealth injection and real-time dashboard.

docs(scheduler): scheduled events always reach the live stream but persist only with the scheduler activity source enabled, and executor failures record as 502

Luigi Agostiafd29c564ce2
diff --git a/docs/architecture/scheduler.md b/docs/architecture/scheduler.md
index b5e1bb8a..ed42af55 100644
--- a/docs/architecture/scheduler.md
+++ b/docs/architecture/scheduler.md
@@ -82,7 +82,7 @@ The orchestrator also implements `RequestAuthorizer`. Before dispatch the execut
### Activity Recording
-The scheduler runs in the same process as the server's activity recorder, so it records each dispatched task there directly through an `ActivitySink` (`internal/server` passes the dashboard-feed recorder into `New`). One event per task carries source `scheduler`, the task's `agentId` and `tabId`, the action kind, and the outcome status and duration once the executor returns.
+The scheduler runs in the same process as the server's activity recorder, so it records each dispatched task there directly through an `ActivitySink` (`internal/server` passes the dashboard-feed recorder into `New`). One event per task carries source `scheduler`, the task's `agentId` and `tabId`, the action kind, and the outcome status and duration once the executor returns. The event always reaches the live dashboard stream (`/api/events`); it is written to the activity log, and so returned by `/api/activity` after a reload, only when `observability.activity.events.scheduler` is enabled, which is off by default like the other non-client sources. Any executor failure, including an instance's own 4xx, is recorded as status `502` with the executor's error text.
This sink is the single source of a scheduled action in the dashboard feed, recorded once and independent of any instance-level recording: