# Defect Report

## DEF-001 — Newly submitted run remains queued and does not expose Report or Logs links

Severity: High
Category: Functional
Requirement: REQ-001
Test Case: TC-005
Environment: https://qa.winds-os.com/ (desktop Chromium 1366x900 and mobile Chromium 390x844)
Evidence: screenshots/TC-005-fail-report-log-links.png

### Description
After a real user submits a QA run from the dashboard, the run appears in history but remains in queued state during the observation window. The Report and Logs columns display dashes, so a product reviewer cannot open the run output or logs from history.

### Steps to Reproduce
1. Log in to QA Agent.
2. Submit a new run from the New test run form with target URL, project, scope, and requirement document.
3. Return to the dashboard history.
4. Refresh/wait for the newest row to expose output links.

### Expected
The history row should expose clickable Report and Logs links for the submitted run, or clearly communicate when links will become available.

### Actual
Newest run row after waiting: qa-20260523-213013	qaagent-functional-pm-qa-ui-create-test	https://qa.winds-os.com/health	queued	—	—	2026-05-23T21:30:13Z	. Links visible: [{"text":"https://qa.winds-os.com/health","href":"https://qa.winds-os.com/health"}]

### Recommendation
Ensure the worker starts promptly and writes a log path soon after submission. Show a useful pending state if report generation is still in progress, and expose Report/Logs links when available.