# Platform changelog

> What's new in the dashboard, routing and docs.

Show: [All](/docs/changelog) · **Platform** · [CLI](/docs/changelog/cli)

Follow along with the [RSS feed](/changelog.xml).

## CI traces in your observability tool

Platform update · [November 14, 2026](/docs/changelog/opentelemetry-traces)

- **Telemetry.** Send each workflow run to your observability tool as an OpenTelemetry trace, with a span for every job and step and the time each job waited for a runner. Spans also say where each job ran, whether the Router retried it, and the CPU and memory it used on your machines. Set it up in **Settings → Telemetry**. See [Telemetry](/docs/dashboard/telemetry).

## Retries, queueing and provider usage

Platform update · [November 13, 2026](/docs/changelog/retries-queueing-and-provider-usage)

- **Automatic retries.** The Router can re-run a job that failed because of its runner, not its own steps: the runner never started it, its machine went offline, or GitHub lost touch with it. The retry routes again, so it can land on a different runner. Turn it on with **Retry jobs when their runner fails** on the Router page, or per repo with [`retry`](/docs/reference/repo-config#retry). See [Automatic retries](/docs/concepts/routing#automatic-retries).
- **Jobs wait for a busy machine.** When every machine that fits a job is busy and nothing later in your runner order can take it, the job now waits for a free slot instead of failing. See [When every machine is busy](/docs/concepts/routing#when-every-machine-is-busy).
- **Skip providers that stop picking up jobs.** When a hosted provider leaves jobs waiting with no runner, the Router sends new jobs further down your runner order until it recovers. See [When a provider stops picking up jobs](/docs/concepts/routing#when-a-provider-stops-picking-up-jobs).
- **Real usage from your providers.** Connect Depot, Namespace or WarpBuild with a read-only token in **Settings → Providers**, and the dashboard pulls your real usage from them every hour.