Review results and troubleshoot

Beta
Follow a live Red Team campaign, interpret its report, and recover from common failures.

After you launch a campaign, Respan opens a live workspace and builds the report in the same view.

Follow campaign progress

Campaign stateMeaningWhat to do
QueuedThe campaign is waiting to runKeep the adapter available when using Connect an agent
RunningProbes and evaluations are activeFollow the live workspace
SucceededThe campaign stopped normally and a report is availableCheck the report status and coverage
FailedThe campaign stopped with an errorFix the displayed problem and launch a new campaign

There is no cancel, pause, resume, edit, or delete workflow. Retrying creates a new campaign.

Live Red Team workspace with the Recon, Breadth, Depth, Verification, and Report stages
The live workspace combines the progress rail, target profile, current attempt, running results, and event log.

The progress rail has five stages:

StagePurpose
ReconProfiles the target, its defenses, refusal behavior, and available tools
BreadthTries a range of adversarial prompt families
DepthRuns adaptive or multi-step attacks when appropriate
VerificationEvaluates responses and confirms evidence
ReportCalculates the final findings and grade

Use Target profile to review what reconnaissance inferred, Current attempt to see the active objective and response, and the event log to understand how the campaign reached a result. Live grades and findings are provisional until report generation finishes.

Read the report

Completed Red Team report with an overall grade, findings, severity distribution, and category results
The final report brings together the grade, summary metrics, confirmed findings, severity, and category coverage.

Start with:

  • Overall grade: A through F when a score is available; ? when no probes completed
  • Confirmed findings: failures supported by campaign evidence
  • Score: a 0–100 blend of confirmed-finding severity and resistance, when available
  • Resistance rate: the share of completed probes that the target refused, when available
  • Probe progress: sent, completed, errored, and planned probes
  • Duration and estimated cost: run time and the engine’s model-activity estimate, when available
  • Severity and category results: where to prioritize review and where coverage was limited

Campaign state and report state answer different questions. A campaign can be Succeeded while its report is not complete:

Report stateMeaning
CompleteThe report summarizes the completed campaign scope
PartialUseful results are available, but some planned probes did not complete
IncompleteToo little of the plan completed for a full assessment; grade and resistance can be unavailable

Always inspect completed and errored probe counts before treating the grade as representative of the planned scope.

An A does not prove that an agent is secure against every attack. It means no severe vulnerability was confirmed within that campaign’s tested scope and budget.

Understand a finding

Open a confirmed finding and review:

  • The decisive prompt and target response
  • The evidence used to confirm the failure
  • The security category and attack technique
  • Severity
  • OWASP or MITRE ATLAS mappings, when present

Prioritize critical and high-severity evidence, then reproduce the issue in a controlled environment. After changing the agent or its safeguards, launch a new campaign to test the updated target.

Red Team campaigns are adaptive, so two runs can use different probes or produce different results. Use the finding details and event log for the run you are reviewing.

Coverage and limits

Black-box campaigns cover risks that Respan can test through the connected conversation interface. Tool-dependent tests run only when reconnaissance detects the required capability. For example, a test that needs customer lookup cannot run when the target exposes no such tool.

Some categories require access that a black-box endpoint does not provide, such as retrieval, embedding, training-data, or response-side controls. Additional access required means the category was not fully testable; it is not a pass or a failure.

Your organization’s current campaign allowance and reset date appear in the campaign creation screen. Avoid using a fixed quota from a copied report because allowances can vary by plan.

Troubleshoot a run

ProblemCheck
Endpoint cannot be reachedHTTPS URL, browser reachability, CORS, firewall, and VPN
Authentication failsHeader JSON and a valid, narrowly scoped credential
Response is rejectedOpenAI-compatible shape with text at choices[0].message.content
Adapter failsopen() creates fresh state and send() accepts and returns strings
WebSocket is rejectedValid Respan API key, current CLI, and outbound access to wss://api.respan.ai/redteam/remote/
Connection dropsFix the connection and launch a new campaign; reconnect and resume are unavailable
Report is not readyWait while the campaign is queued or running
Allowance is exhaustedUse the reset date shown in the campaign UI

If a campaign fails, fix the displayed error before launching its replacement. A succeeded campaign with missing probes should be reviewed as partial coverage, not silently treated as complete.

Handle report data safely

Reports can contain attack prompts, target responses, reconstructed instructions, secrets, personal data, and details about connected tools. Restrict access to the report and any copies you create.

Use non-production targets where possible, keep credentials narrowly scoped, and grant an adapter only the network and tool access required for the assessment.