Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Deploy Rolled Back Error Block for React

A full-screen page for a rolled-back deploy: a line chart of one metric against its limit with the health check, rollback and recovery pinned to it, and a switch between three metrics.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Show a rolled-back release as the line that caused it, with this deploy rollback page for React with Base UI. It's a whole screen with the page's rails and one band across it, split with the chart first. In a framed figure, a hand-built line chart draws one metric by minute from 14:00 to 14:14 UTC with a dashed limit and a thick stroke where the line is over it, and three numbered pins for the health check failing, the rollback beginning and the recovery, listed in words under it. A Toggle Group switches between Error rate, p95 latency and CPU, each with its own limit and series, and a Before, Peak and After strip is worked out from the series. At the other side are the headline, the one Shine Button View deploy logs and two cells for the version that was tried and the one that is live. The band's rules and the chart's frame come from Guides, and the entrance is CSS only. For a release manager, a deploy tool or a status page.

FAQ

What is real here, and what stays local?

Nothing was deployed. The three series, the limits, the versions and the three events are typed in the file, and the link points nowhere. To wire it for real, fill METRICS from your monitoring, keep the pins as the events your tool recorded, and point View deploy logs at your logs.

How is the chart built, and is it readable without seeing it?

It is a plain SVG path and a few boxes in a left-to-right frame, no chart library, drawn in foreground weights with no color for good or bad. The chart has a text description that gives the metric, the limit, when it crossed it and when it came back, the pins are listed as an ordered list with times and words, and the Before, Peak and After strip repeats the numbers in text.

Where do the numbers under the chart come from?

From the series itself. The crossing is the first reading over the limit, the recovery the first one back under it, Before is the average of what came earlier, Peak the highest reading in between and After the average from the recovery on, so the text and the drawing cannot disagree. The three pins are fixed events and the same for every metric.

How does the metric switch work?

It is a single-choice group that can never be empty: pressing the chosen one keeps it. Choosing another redraws the chart in the same box with its own axis, limit and thick stroke, and the status line says when it crossed and recovered. Nothing on the page changes size.

Does it work in a right-to-left page?

The chart, its axis and its pins stay left to right, because time runs one way, and so does the Before, Peak and After strip. The headline, the sentences and the version cells follow the page direction.

What changes on a phone?

The headline, the button and the two version cells come first, then the metric switch, a shorter chart and the events. The chart's caption and the version cells' dates stay for screen readers and are hidden from sight, so the page fits in about one and a half screens.

  • Pro

    A CI build window: five pipeline stages as tabs, each with its own numbered log, the failing line marked, a re-run that only queues, common fixes and the build id with Copy.

  • Pro

    A migration ledger after a failed migration: five rows with their states, the database error in a numbered window, a retry that fails again, and a roll-back that says exactly what it reverts.

  • Pro

    A full-height page for a web app tab running a retired version: a ruler of five releases with the supported range shaded and You are here marked, a radio group to read each release, three changes in 5.0 and a reload button.

  • Pro

    API Uptime Strips Error

    Server and outages

    A full-screen outage page for an API host: the display 503, a notify-me form that saves in the page, and four APIs as rows of thirty day-cells with a shape and a word for today and an uptime counted from the minutes.

  • Pro

    Rollback Wizard Changelog

    Deploys and rollouts

    A three-step rollback wizard in one framed window: pick a previous release, review what reverts and what stays, then type the version to unlock a Shine Button that opens an alert dialog and ends on a stated demo result.

  • Pro

    Failed Test Run Error

    Developer tools

    A test-runner window: a tree of suites and tests with their results, a Failed only switch, and a pane that compares expected and received values with the differing characters underlined.