Changelog

The measurement control page could time out on procedures with millions of measurements, leaving the Pareto charts unable to load.

• Fixed the measurement control page timing out on large procedures, so the Pareto and Cpk charts load reliably.
• Improved how historical measurement data is aggregated in the background, keeping the page fast as your data grows.
• Fixed the live runs toggle getting stuck on "Reconnecting" after a connection drop.

Tightened the checks behind the dashboard's automatic rendering optimizations, so the UI stays fast and dependable as it grows.

• Strengthened safeguards around how components render and update
• Fixed several edge cases surfaced by the new checks
• Resolved two subtle display glitches in the process

Reduced the shared code that every dashboard page loads, so navigation feels lighter across the app.

• Shipped only the English text for validation messages instead of every language
• Loaded search, notifications, and analytics on demand instead of up front
• Cut roughly 300KB from the code shared by every page

Charts on the measurement, chat, and report pages now load on demand instead of up front, so the pages open faster.

• Deferred chart rendering until it's actually shown
• Loaded the code viewer only for measurements that use it
• Trimmed the initial load across all three page types

The station detail page now loads noticeably less code up front, so it opens faster.

• Removed a heavy charting library from the initial load by drawing the telemetry sparklines directly
• Loaded the realtime connection only when it's actually needed
• Cut about 900KB of JavaScript from the page's first load

The dashboard now loads less code up front and re-renders more efficiently, so pages feel faster across the board.

• Trimmed the JavaScript loaded on every page, with the heaviest detail pages cut the most
• Charts, search, and other heavy panels now load on demand instead of up front
• Enabled automatic rendering optimizations for smoother interactions

When a list page failed to load, a network or server error looked identical to having no data — now it's clearly an error you can retry.

• Added a dedicated error state with a "Try again" action across runs, units, logs, batches, API activity, and procedures.
• Kept existing rows on screen when a "load more" fails, so a failed fetch no longer wipes the list.

Scrolling to load more entries on the changelog, news, and guides pages could crash the page instead of fetching the next batch.

• Fixed the load-more pagination so infinite scroll reliably loads older entries on changelog, news, and guides.

When a list page failed to load, it used to look empty, as if there was no data. It now shows a clear error with a retry button.

• Added a proper error state with a "Try again" button to the runs, units, logs, batches, and other list pages
• A failed load no longer looks like an empty page

Navigating between pages now shows a thin progress bar at the top, so it's clear when the next page is loading.

• Added a slim loading bar that animates across the top during navigation
• Matches the light and dark themes