Balena incident

Unable to pin releases in the dashboard

Minor Resolved View vendor source →

Balena experienced a minor incident on April 10, 2025 affecting Dashboard, lasting 1h 40m. The incident has been resolved; the full update timeline is below.

Started
Apr 10, 2025, 01:00 PM UTC
Resolved
Apr 10, 2025, 02:40 PM UTC
Duration
1h 40m
Detected by Pingoru
Apr 10, 2025, 01:00 PM UTC

Affected components

Dashboard

Update timeline

  1. investigating Apr 10, 2025, 01:00 PM UTC

    We are currently investigating an issue with users unable to pin releases in the dashboard.

  2. identified Apr 10, 2025, 01:00 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 10, 2025, 01:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 10, 2025, 02:40 PM UTC

    This incident has been resolved.

  5. postmortem Apr 14, 2025, 12:52 PM UTC

    A UI update included updates to a few nested dependencies, which changed a behavior we relied on. The result was preventing the data population of available releases in the Target Release section on the Fleet Summary page. We initially reverted the changed package, and subsequently changed our approach so that it works with the latest version of the package.