# Visualization issue in Kibana dashboard after upgrade to v8.17.1 **URL:** \ **Category:** Kibana\ **Tags:** dashboard, visualisation\ **Created:** [February 3, 2025, 11:33am UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012 "2025-02-03T11:33:00Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![SaraAlshamsi](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@SaraAlshamsi](https://discuss.elastic.co/u/SaraAlshamsi)\ **Post date:** [February 3, 2025, 11:33am UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012/1 "2025-02-03T11:33:00Z")
Hello, I have an issue with some visualization objects after we upgraded Kibana to v8.17.1. I created a dashboard when Kibana was v8.15.3. The dashboard contained multiple objects such as TSVB (markdown), Vega, lens (metric, line and gauge). After we upgraded to v8.17.1, the TSVB (markdown) and Vega started to show the following message while editing the dashboard: ![kibana error](https://us1.discourse-cdn.com/elastic/original/3X/a/9/a92eb2d1df2021e8027b516e1c7a12d6109b5da0.png) I thought first because the markdown was already created before the upgrade, it got affected. But, I tried to create a new TSVB (markdown) object, and it showed the same error while editing the dashboard. This error appears also when I create a duplicate of the TSVB (markdown) object. After I created a duplicate, I edited/updated the text, saved it and went back to the dashboard. Instead of seeing the new text, I see the error. The same happened with Vega. Suddenly, it disappears and shows this message. I had to remove these objects whenever they show this message and import them again multiple times from the library which is not convenient. This happens randomly whenever I edit the dashboard (not everytime). Eventually I was able to update my dashboard but after multiple times of removing these objects and importing them again. Maybe there is an issue with the "Edit" functionality of the dashboard? Is this a bug in the new release? Thank you. ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [February 3, 2025, 2:38pm UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012/2 "2025-02-03T14:38:15Z")
Sorry for the inconvenience. It seems you are hitting this issue, I'll put a comment there referencing to this post, in case there are details you shared useful to the engineers. > > > \*\*Describe the bug:\*\* > > It is possible to break a Visualize panel in a dashboard …by saving it into library and returning back to the dashboard. > Reloading will make the error disappear. > Unfortunately if other actions are performed after this issue, this trigger another worst issue described in #206922 > > \Image > > \*\*Steps to reproduce:\*\* > 1. Create a dashboard > 2. Add an Agg based panel > 3. Save the dashboard > 4. Edit the panel and click on "Save to library" within the editor > 5. Set a name (keep the "Add to Dashboards after saving" enabled) > 6. Click on "Return to dashboard" > > \*\*Expected behavior:\*\* > > The panel shown a chart, but with the "Unlink action" available within the context menu ---
**Author:** ![SaraAlshamsi](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@SaraAlshamsi](https://discuss.elastic.co/u/SaraAlshamsi)\ **Post date:** [February 12, 2025, 10:25am UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012/3 "2025-02-12T10:25:30Z")
Thank you for your reply. I understand that there is no solution for this issue yet? Regards, ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [February 12, 2025, 11:02am UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012/4 "2025-02-12T11:02:11Z")
There's an open Pull Request to fix this issue, you can check on the labels the expected versions will get it > > > Fixes https://github.com/elastic/kibana/issues/206921 > > \### Problem > The visual…ize embeddable is inconstant when passing runtime state to \`buildEmbeddable\`. Sometimes, only \`{ savedObjectId }\` is provided. The embeddable tried to work around this by calling \`deserializeState\` in \`buildEmbeddable\`. > > There was a different bug with the \`deserializeState\` guard in \`buildEmbeddable\` where state like \`{ savedObjectId, savedVis: {} }\` would not pass the guard. Dashboard adds runtime state so \`savedVis\` was getting added to \`initialState\` and thus failing the guard > > This resulted in the visualize embeddable trying to initialize with state \`{ savedObjectId }\` instead of state in the shape \`{ savedObjectId, serializedVis: {} }\`. This resulted in error message like "Could not read properties of undefined" when the embeddable tried to read from \`state.serializedVis.type\`. > > \### Solution > The solution is to ensure that \`buildEmbeddable\` is always passed runtime state containing \`serializedVis\`. This pattern is in line with the lens embeddable. > > \### Test instructions > \* install sample web logs > \* create agg based visualization > \* create new dashboard, add agg based visualization. Open context menu of vis and select "Unlink from library". (Side note, removing legacy visualizations from add panel makes it hard to add by-value agg based visualizations to a dashboard) > \* save dashboard > \* edit agg based vis > \* Click "Save to library" and fill out form > \* Verify visualization is rendered in dashboard. ---
**Author:** ![Vishal\_Reddy\_P](https://avatars.discourse-cdn.com/v4/letter/v/e5b9ba/32.png) [@Vishal\_Reddy\_P](https://discuss.elastic.co/u/Vishal_Reddy_P)\ **Post date:** [June 3, 2025, 5:09pm UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012/5 "2025-06-03T17:09:22Z")
Hi, I wanted to bring to your attention that the above issue seems to persist in version 8.18.1. After upgrading from 8.12.1 to 8.18.1, I've encountered problems when creating dashboards with multiple visualization objects. Occasionally, the dashboard becomes corrupted, even when creating entirely new visualization objects or duplicating existing ones. The errors I receive vary, including "Invalid Visualization Type," "Visualization lens not found," and "Cannot read properties of undefined (reading 'filters')." These errors occur randomly, and I haven't been able to consistently reproduce them. For your information, I'm not saving the visualization lens in the library; instead, I'm embedding, editing, and saving it directly. I'm hoping for a resolution to this issue, but I'm unsure how to formally report it without a clear method to recreate the problem. Thank You ---
**Author:** ![Cory34](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cory34/32/112268_2.png) [@Cory34](https://discuss.elastic.co/u/Cory34)\ **Post date:** [June 4, 2025, 4:06am UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012/6 "2025-06-04T04:06:43Z")
I have the same issue after the upgrade. It's hard to replicate but it happens often. I also get a similar issue with all my map layers suddenly disappearing from the map (except the base layer). My workaround here is to hit the back browser button multiple times until an instance appears whereby the map layers return. ---
**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\ **Post date:** [June 4, 2025, 3:35pm UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012/7 "2025-06-04T15:35:10Z")
@Vishal_Reddy_P @Cory34 are either of you using lab setting [Defer loading panels below the fold Lab](https://www.elastic.co/guide/en/kibana/8.14/dashboard-troubleshooting.html)? There is a known issue, [panel state lost if dashboard saved and panel is not initialized](https://github.com/elastic/kibana/issues/220799), where panel state could be lost on save with "Defer loading panels below the fold Lab". A fix has been pushed in 8.18.2 ---
**Author:** ![Cory34](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cory34/32/112268_2.png) [@Cory34](https://discuss.elastic.co/u/Cory34)\ **Post date:** [June 4, 2025, 4:48pm UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012/8 "2025-06-04T16:48:50Z")
Hi Nathan, I'm aware of that feature but don't use it. Thanks. ---
**Author:** ![Vishal\_Reddy\_P](https://avatars.discourse-cdn.com/v4/letter/v/e5b9ba/32.png) [@Vishal\_Reddy\_P](https://discuss.elastic.co/u/Vishal_Reddy_P)\ **Post date:** [June 4, 2025, 6:01pm UTC](https://discuss.elastic.co/t/visualization-issue-in-kibana-dashboard-after-upgrade-to-v8-17-1/374012/9 "2025-06-04T18:01:29Z")
@Nathan_Reese , Yes, I do have the "Defer loading panels below the fold (Lab)" setting enabled but for only Kibana. Based on what you've shared it seems likely that this setting could be causing the issue, especially if the panel state is lost saving before initialization. Thank you