# Kibana 8.8.8 external plugin failure

**URL:** <https://discuss.elastic.co/t/kibana-8-8-8-external-plugin-failure/335240>\
**Category:** Kibana\
**Tags:** docker, kibana-plugin-development\
**Created:** [June 5, 2023, 3:30pm UTC](https://discuss.elastic.co/t/kibana-8-8-8-external-plugin-failure/335240 "2023-06-05T15:30:22Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [June 8, 2023, 3:39pm UTC](https://discuss.elastic.co/t/kibana-8-8-8-external-plugin-failure/335240/9 "2023-06-08T15:39:33Z")

</div>

> [@kbujold\_wr](#):
>
> That is our external plugin name. There is an issue with it with the build only. We do not know why it works in dev but not in the build.

Not sure what the issue is, but recently I saw a post about another custom plugin that works while in `dev` mode but not in `prod` mode.

It was this [one](https://discuss.elastic.co/t/enhanced-table-plugin-on-elastic-cloud/335214/3).

---

_[View the full topic](https://discuss.elastic.co/t/kibana-8-8-8-external-plugin-failure/335240)._