// red team
Running reports
Follow a red-team run from provisioning to results, and know what to do when one fails.
Reports run asynchronously in an isolated sandbox, so creating one returns immediately while the real work continues in the background. The report's detail page is where you follow along.
The lifecycle
Three status fields tell you where a run stands:
| Field | Values |
|---|---|
| Report status | In progress, In review, Done, Failed |
| Sandbox status | Pending, Provisioning, Ready, Failed |
| Agent status | Pending, Installing, Running, Completed, Needs Review, Failed |
A healthy run moves from provisioning to running to In review, where results wait for your decision. Failures in provisioning or execution land on Failed with safe error context.
Reviewing results
| Signal | Where to look |
|---|---|
| Overall status | Report detail header and the Red team list |
| Agent activity | The live event feed on the detail page |
| Findings | The report's findings section and the org-wide Findings queue |
| Evidence | Recordings and screenshots on Web app reports |
Web app reports also show the browser session live while the agent works, and a recording afterwards. See Web app reports.
Rerun or automate
Web app reports can be rerun from the detail page. Repository reports can trigger automatically on a GitHub release, a tag, or a schedule instead of manual creation.
To wire the lifecycle into your own systems, subscribe to report.started and report.finished webhooks. report.finished fires once per report, with the outcome and a link back to the dashboard.
When a report fails
- Confirm the GitHub App still has access to the target repository.
- Verify the repository exists and is selected in the app installation.
- For Web app reports, check that the target URL is public and your WAF allows the scanner.
- For agent reports, check that the description and type match the system you intend to test.
- See Troubleshooting.