I've been conducting a detailed analysis of our GRC platform costs, and my workflow heavily depends on the custom dashboard views within LogicGate to track control performance and exception rates across different business units and cloud providers (specifically AWS and Kubernetes clusters). Following the latest platform update (I believe version 10.2.7 was applied to our instance over the weekend), I am experiencing a persistent issue where complex, multi-criteria filters on my primary dashboards are failing to save upon browser refresh or session logout/login.
The specific filter configuration I am attempting to preserve involves a nested set of conditions across several object types. For example:
* **Primary Object:** `Control Assessments`
* **Filters:**
* `Status` is not `Closed`
* `Business Unit` is one of `CloudOps`, `FinOps`, `InfraSec`
* `Related Cloud Provider` contains `AWS`
* `Last Updated Date` is within the last `30` days
* A custom `Cost Impact` field is `High` or `Critical`
I build this view, apply it, and save the dashboard. The UI confirms "Dashboard saved." However, upon a full page reload or when I return to the dashboard later, the view has reverted to a default or previously saved state, losing the most recent filter stack. This is severely disrupting my ability to monitor ongoing issues, as I must manually reconstruct the filter set multiple times per day.
**Troubleshooting performed so far:**
* Confirmed the behavior in both Chrome 124+ and Firefox 125+.
* Cleared browser cache and local storage for the LogicGate domain.
* Verified my user permissions have not changed (I am a full Administrator).
* Created a simpler filter (e.g., only `Status` is not `Closed`), which *does* seem to persist.
* The issue appears correlated to the number of filter conditions and the inclusion of certain field types, like the custom `Cost Impact` picklist and the `Related Cloud Provider` relationship field.
This feels analogous to a parameter limit issue one might encounter with AWS Cost Explorer saved views or complex Grafana dashboards, where an overly long query string or deeply nested JSON structure is not being serialized/deserialized correctly by the UI's state management.
**My questions for the community:**
* Is anyone else observing this behavior post-update, specifically with dashboards utilizing more than 3-4 filter conditions or custom fields?
* Has anyone discovered a workaround, perhaps involving the order in which filters are applied, or by saving the view as a "Public" report first before adding it to the dashboard?
* From a technical perspective, could this be related to the underlying filter model exceeding a new, unstated character limit or depth in the latest API?
The manual rework is incurring a non-trivial operational overhead. I've begun tracking the time lost in a spreadsheet, and it's already amounting to several person-hours per week across my team. Any insights or shared experiences would be valuable before I escalate a formal support ticket with our CSM.
-cc
every dollar counts