Excel-like Tables for Confluence Data Center

Critical Incident Notice – Required Upgrade

Impact summary: An unexpected expiration of the embedded SpreadJS license caused spreadsheet components to fail to initialize, rendering the affected app screens unusable. Users observed an error indicating the SpreadJS license had expired.

Incident overview

A licensing token bundled with the spreadsheet rendering library (SpreadJS by MESCIUS) reached its expiry. When the library validates the key at runtime, the UI blocks spreadsheet initialization and displays a license error. Because key pages depend on the component, core functions became unavailable until the library key was refreshed via an app update.

Scope and symptoms

  • Scope: Affects environments running the legacy SpreadJS-licensed component embedded in the app, across Platform 6 and Platform 7 builds.

  • Primary symptom: Sheets fail to load; a message referencing an expired SpreadJS key appears; pages relying on the grid become non-functional.

  • No data loss: Underlying data remains intact; only the UI rendering is blocked by the library’s license gate.

Root cause analysis

The app included a time-bound SpreadJS deployment key subject to periodic renewal. The packaged key was beyond its validity window, and the runtime check in the library halted rendering. Environments without timely updates inherited the expired token.

Resolution

Upgrade the app to a version that contains a refreshed SpreadJS license key.

  • For Platform 6: Upgrade to version 2.0.2.

  • For Platform 7: Upgrade to version 1.2.9.

These releases replace the expired key with a valid license bundle and restore spreadsheet rendering and all dependent features.

Upgrade guide

  1. Identify platform family and target version:

    • Platform 6 ➜ install 2.0.2

    • Platform 7 ➜ install 1.2.9

  2. Back up your instance configuration and capture current app version.

  3. Perform the app upgrade through your administration console’s app management screen.

  4. Clear application and browser caches where appropriate, then reload an affected page.

  5. Validate fix: Open several pages using the spreadsheet UI, confirm no license banner appears, and that grid operations (view, edit, save, copy/paste) work.

Verification checklist

  • App version matches 2.0.2 (Platform 6) or 1.2.9 (Platform 7).

  • No SpreadJS license error banners on load.

  • Sheets render with expected data and formatting; editing and saving succeed.

Temporary workarounds (if upgrade is delayed)

  • Use alternative non-grid views or exports (where available) to access data while planning the upgrade.

  • Restrict access to grid-heavy pages to reduce user impact until the upgrade is completed.

Prevention and long-term actions

To avoid recurrence, adopt a maintenance cadence and monitoring for third-party runtime licenses embedded in apps.

  • Proactive updates: Track app release notes and apply maintenance releases that refresh third‑party keys.

  • Environment monitoring: Add health checks for grid initialization errors to alert operations teams early.

  • Lifecycle policy alignment: Keep host products and apps within supported ranges to ensure timely fixes.

FAQs

Why did the app stop working instead of falling back gracefully?

The embedded library enforces a license check at runtime. On failure, it blocks initialization to comply with vendor licensing terms, which in turn prevents the grid UI from rendering.

Is any customer data at risk?

No. The incident affects UI rendering only. Stored data and backend records remain unaffected.

Which versions contain the fix?
  • Platform 6: 2.0.2

  • Platform 7: 1.2.9

What if upgrading is not possible immediately?

Limit use of grid pages and switch to alternative views to maintain continuity. Plan an expedited maintenance window to install the fixed version.