New pattern to design effective error messages

A good error message can turn a dead end into a recoverable step. The new Error messages pattern brings together everything you need to design clear, consistent error messages across your app, whatever component you're working with.

Start with the right component or pattern

Where and when you show an error matters as much as the words you use. A field validation error, a Toast, and a MessageContainer can all communicate failure, but with different weight and urgency. The pattern gives you a shared starting point: which component to reach for, how to match the visual weight to the severity, and where to place the message so it's as close to the problem as possible.

That consistency adds up. Across teams and features, a common approach means users get a predictable experience no matter what went wrong.

Write effective copy

The pattern covers key principles for writing effective error messages, each with a side-by-side do/don't example drawn from real Dynatrace UI copy:

• Use simple words
• Be specific
• Show a way forward
• Skip obvious next steps
• Avoid generic errors or raw codes
• Don't assign blame
• Don't be overly apologetic
• Don't exaggerate or downplay

These principles also make a good prompt checklist when you're using an LLM to generate or review error copy. Pattern pages are designed to be the foundation your content is built on, so you can scale without losing consistency.

Read the full pattern in the Error messages reference.