Changes / Lattice / Admin Compensation Cycle Recommendations page showing "Something Went Wrong" error
Lattice: Major incident: Admin Compensation Cycle Recommendations page showing "Something Went Wrong" error
Summary
Lattice reported a major incident affecting the admin Compensation Cycle Recommendations table, which showed a "Something Went Wrong" error, starting 2026-08-21 16:30 UTC. It was resolved at 2026-08-21 18:24 UTC, lasting 1 h 53 min. A fix was deployed; admins were instructed to refresh the page to see data successfully.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Admin Compensation Cycle Recommendations page showing "Something Went Wrong" error
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-08-21 16:30 UTC
Before: not present
After: 2026-08-21 18:24 UTC
Before: not present
After: Lattice Application
Before: not present
After: Lattice is currently experiencing an incident on the admin Compensation Cycle Recommendations page. The Recommendations table is showing a "Something Went Wrong" error.
Before: not present
After: Our team has identified the underlying root cause and and is implementing a fix to resolve the error admins see on the Compensation Cycle Recommendations page.
Before: not present
After: A fix has been deployed. Admins viewing Compensation Cycle Recommendations should refresh the page and see data successfully. We will continue monitoring for the time being.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Admin Compensation Cycle Recommendations page showing "Something Went Wrong" error (this change) Lattice reported a major incident affecting the admin Compensation Cycle Recommendations table, which showed a "Something Went Wrong" error, starting 2026-08-21 16:30 UTC. It was resolved at 2026-08-21 18:24 UTC, lasting 1 h 53 min. A fix was deployed; admins were instructed to refresh the page to see data successfully. | Major incident |