Error State

Generalizes the retry-panel recipe first proven in the Pricing Engine into the design system, so every data-driven component composes the same failed state instead of hand-rolling its own retry button and copy.

Props

Do / Don't

• Do omit onRetry when there's genuinely nothing to retry (a one-time action that already ran) — the retry button only renders when the callback is provided, so this is just "don't pass one" rather than a separate prop to disable it.
• Do put the actual failure detail in description, not just "Something went wrong" twice — the title's default already says that; the description is where the user learns what to do next.
• Don't build a bespoke inline error banner for a section's failed fetch — ErrorState (or a DataTable with its error prop set, which renders this) is the one shape for that across the system.