Monitoring
Live screen streaming, video replay, structured errors, and troubleshooting failed executions.
reArray provides realtime and retrospective visibility into every execution — from live browser screens during a run to recorded video after completion.
Executions list
Open Executions in the workspace sidebar for a live-updating list. Each row shows:
- Status badge with current lifecycle state
- Task and agent names
- Start time and elapsed duration
- Reference (if set)
The list updates in realtime as executions progress.
Execution viewer
Click an execution to open the viewer dialog:
Live stream
While status is running, the viewer shows a live screen stream from the agent's browser session. Screenshots broadcast via Supabase Realtime give near-real-time visibility without polling.
Use live stream to:
- Confirm the agent reached the expected page
- Watch multi-step flows progress
- Diagnose stuck runs before they time out
Video replay
After completion, reArray records session video stored in the executions artifacts bucket. The composite player merges timelines when a task spans multiple platforms.
Retrieve signed video URLs via API:
GET /api/v1/integrations/executions/{id}/artifacts
Signed URLs expire after 5 minutes (expires_in_seconds: 300).
Result and params
On completed executions, inspect:
- Result — Final output set by
terminate valueor last extracted values - Params — Input values passed at run time
- Metadata — Caller-supplied correlation data
Structured errors
When status is error, the viewer shows:
- Error message — Human-readable description
- DSL location — The script fragment where the failure occurred (action, selector, line context)
Common error causes:
| Symptom | Likely cause |
|---|---|
Timeout on wait visible | Selector mismatch, slow page, or wrong platform state |
| Assert failure | Expected condition not met after actions |
| Auth error | Expired session, wrong credentials, or missing login guard |
| Unknown handler | Platform handler in DSL not attached to the agent |
$secrets error | Secret referenced outside in handler { } block |
Use the DSL location to jump to the failing line in the task editor.
Troubleshooting guide
Execution stuck in queued
- Check agent concurrency limits — max workers may be saturated
- Verify the agent is attached to all platforms the task requires
- Check per-platform
max_concurrent_taskson the agent-platform binding
Login failures on repeat runs
- Implement the session-aware login pattern
- Check vault credentials are current
- Review video replay to see which page state the agent encountered
Intermittent selector failures
- Add fallback selector chains:
{ css "#btn" text "Submit" } - Increase
waittimeouts for slow pages - Use
extract ... defaultfor optional elements
Webhook not received
- Verify
callback_urlwas included in the API request - Check the Integrations delivery log for failed deliveries
- Test your handler with
POST /api/v1/integrations/webhooks/test - See Webhooks for signature verification
Aborting stuck runs
If an execution is stuck in running:
- Open the execution viewer and click Abort
- Or call
POST /api/v1/integrations/executions/{id}/cancel - Review video replay and error details to fix the script before re-running