Mars 2026

March 4, 2026

ScreenPlay execution traces available in Orchestrator

ScreenPlay HTML execution traces are now available directly in Orchestrator, for published automations after robot run. Previously only accessible in the local Logs/ScreenPlay folder when running or debugging from Studio, traces now serve as a centrally accessible execution record, showing what the agent actually saw and did, essential for root-cause analysis and auditability in large-scale automation.

Surfacing traces in Orchestrator enables you to:

• diagnose ScreenPlay executions without requiring local access or manual log collection.
• gain full transparency into how automations interacted with the screen.
• archive or review traces centrally, aligning with enterprise audit requirements.
• perform cross-run comparison and analyze automation resilience over time.