How-to Guide
Manage test artifacts
Access logs, screenshots, traces, and exports from completed runs.
Objective
Access logs, screenshots, traces, and exports from completed runs.
Prerequisites
- Completed run
Procedure
Open run detail
Runs → select run → artifacts or logs tab.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Confirm organization and team context in the Console header before making changes.
Download artifacts
Export logs, screenshots, or traces as available.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Note project, run, or agent IDs if you may need support escalation.
Attach to tickets
Link artifacts to issue tracking integrations.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Artifacts available for debugging and audit.
Was this page helpful?
