Error message

Under ReviewUpdated May 12, 2026

Consider the error situation

When creating an error message, ask the following questions. The answers will help determine which component to use and where to place it.

Errors on a page

Errors in a sidebar

Error	Description	Component
Global error	Generated by the system or API.For example, the system cannot connect to the network or data is not sent from a related system because of problems with the system.Cannot be resolved by the user.	Message full-width and pinned to the bottom of the app bar (pushing the rest of the content down).orError state in the associated data container. For example, a dashboard, table, tile, sidebar, or full page.
Background process error	Background process fails.Can be caused by a previous action on the same page or a previous page.For example, automatic data import cannot be completed.Usually requires user intervention to resolve the error.	Message above the page content, below the top navigation bar.Note: Display error messages generated by asynchronous actions in the notification center.
Permissions error	There are issues with the user's account (not the user input).For example, the user has reached their maximum limit for adding items.Cannot be resolved by the user.	Message below the sidebar content.

Error	Description	Component
Component error state	User input does not meet data or format requirements for a component.There is an error state for the component.	Message at the top of the page with links to the error state message for each affected component.
Validation error	User input meets a component's data and format requirements.There's a different issue with the input. For example individual figures have an incorrect total or there's no match for the data in the database.	If the component is in a sidebar: message above the sidebar content.If the component is on the main page: message close to the affected component.
Data input error	User input is not in an accepted format.There is no error state for the component and no space to display a message directly above it. For example, a table with an error on a table row.	Message close to the affected component.
Data access error	Configuration is needed so the user can access the data.The user does not have permission to view the data.	Error state in the associated data container. For example, a dashboard, table, tile, sidebar, or full page.
Unsupported action	The user tries to perform an unsupported action. For example, upload an unsupported file type.	Error state in the associated data container. For example, a dashboard, table, tile, sidebar, or full page.

Use the active voice in the present tense.
Use direct, plain language to explain what happened, why it happened, and how to fix it.
Provide reassurance, empathize with the user, and do not blame them.
Give the user a way out of the situation.
Use specific error messages for specific error states. Avoid generic error messages where possible.
Do not use exclamation marks or all capital letters.
Do not include error codes or technical jargon.
Avoid using sorry, must, or please.

Helpful error message

Unhelpful error message

Error type	Example error message
User action error.	For error message examples, see Message and Error state.
Error state message for a specific component.	Post revenue to an open period.Add a bill.Select an open GL account.Enter a due date. Use the format DD/MM/YYYY. Change the base currency for the transaction.

Date	Change
10 Sep 2025	Removed 'Data conflict' for copilot.
15 May 2025	New added Data conflict in User action errors.
September 2024	New version created. Previous version archived in the frozen Product design system.