How-to Guide
Rerun a failed test
Re-execute a failed validation after fixes or environment correction.
Objective
Re-execute a failed validation after fixes or environment correction.
Prerequisites
- Prior failed run exists
Procedure
Open failed run
Navigate to Runs and open the failed run detail.
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.
Analyze failure
Review logs, artifacts, and case outcomes.
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.
Rerun
Trigger rerun for failed cases or full run.
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
New run reflects updated application state.
Was this page helpful?