# Issue pages open on metric cards, log summaries and blast radius

Issue pages lead with the evidence

> Published 2026-07-03 · Updated 2026-11-18 · Canonical: https://polylane.com/changelog/2026-07-03-issue-pages-lead-with-the-evidence/

Issue pages now open with the evidence Polylane saw: metric cards against their baselines, a log summary and the resources around the affected one, for anyone deciding how urgent an issue is.

## What changed

Issue pages now open with what Polylane saw. Metric cards show each signal's value, its baseline and how far it moved, for example three times the baseline. A log summary counts errors, warnings and info lines over time and groups the lines that matter by their shape, with a count for each.

### Blast radius

Every issue shows the resources around the affected one in the context graph, so you can see what else is exposed before you open the investigation.

## Investigations survive deploys and restarts

A deploy or restart on our side no longer cuts an investigation off mid-turn: it picks up where it stopped.

## Why it matters

The first question about any issue is how bad it is and what it touches. Leading with the numbers, the log lines and the neighbouring resources answers that on one screen, before you read the investigation or open another tool.

## How to use it

1. Open **Issues** in the console and select an issue.
2. Read the metric cards for how far each signal moved from its baseline, then the log summary for the line shapes that changed.
3. Check the blast radius for the resources that depend on the affected one, then open the investigation for the cause.

## Related

- [Context graph](https://polylane.com/product/context-graph/)
- [Investigations](https://polylane.com/product/investigations/)
- [Cloudflare integration](https://polylane.com/integrations/cloudflare/)

## Improvements

- Cloudflare: New checks watch Hyperdrive queueing, Logpush failures, Durable Object errors and memory, Workflow retries, Workers AI, Vectorize, Browser Rendering and Tunnels
- Cloudflare: Durable Object namespaces chart their SQL storage over time
- Onboarding: Onboarding has steps to connect GitHub and Slack
- Sentry: Webhooks from Sentry are verified with your integration's client secret
- Investigations: When a model provider is at capacity, Polylane falls back to another model
- AWS: X-Ray traces too large for one call come back as whole segments

## Fixes

- Investigations: Stalled turns are swept automatically
- Issues: Bot probe floods against paths like `wp-login.php` and `.env` no longer open issues
- Sentry: Long Sentry alert titles are trimmed to a readable length

[All updates](https://polylane.com/changelog/)
