Linear - Error States
We analyzed 8 examples of how Linear handles error states across their product, spanning 4 different approaches: inline validation, toast notification, in-context error, full-page error.
Inline Validation
Linear — Workspace invite modal
Invite to workspace modal with an invalid email address entered in the Email field. The modal is overlaying the main workspace view which also shows a partially visible 'Problem loading data' error behind it.
Toast Notifications
Linear — My Issues > New issue modal
Two stacked toast notifications in the bottom-right corner triggered by attempting to attach a file that exceeds the size limit in the New Issue creation modal. The top toast is a warning-style upsell, and the bottom toast is a red error notification.
Linear — Settings > Import / Export
Toast notification in the bottom-right corner of the Settings > Import / Export page, triggered after a failed CSV export attempt while offline.
Linear — New issue modal
Toast notification in the bottom-right corner triggered by attempting to create a new issue without entering a title. The New Issue modal is open with empty title and description fields.
Linear — Settings > Emojis
Toast notification in the bottom-right corner of the Settings > Emojis page, triggered after attempting to upload a custom emoji image that exceeds the maximum allowed dimensions.
Linear — Settings > Security & access
Toast notification in the bottom-right corner of the Settings > Security & access page, triggered when sessions fail to load due to a network error.
Full-Page Errors
Linear — Main content area (offline)
Full-page error state shown in the main content area when the app cannot load data while offline. The sidebar navigation remains visible with an 'Offline 4' status indicator in the top bar.
In-Context Errors
Linear — Issue detail view (invalid URL)
In-context error state shown in the main content area when navigating to a non-existent issue. The sidebar remains visible. An illustration of a broken/errored document is displayed above the error message.