Plug-ins suddenly switching to unverified when they are resubmitted is causing end users to panic thinking that the OpenAI has marked the plugin as “dangerous”. The red shield looks to a lot people like some kind of danger signal.
2 Likes
I removed a bunch of unverified plugins, better safe than sorry.
That’s unfortunate - there’s really no reason to do this.
What we need instead is a version control system where OpenAI caches a previously approved plugin until the new version is approved, so users have a better experience and app makers have no downtime.
I’m sure they’ll get to it 
1 Like
It’s not really possible to do this since people can change the server side code, having a cached version will just make it so all the plugin calls error out if the code on the server has changed but we used a cached version of the OpenAPI spec for example.
In general, thinking about how to make this seamless, but it is a net good thing that people are uninstalling unverified plugins, that is the whole intent of the way of the way the system is designed.
1 Like
The reason to do this is OpenAI has no longer validated that this service passes the Trust and Safety checks of the plugins in the store. The plugin could have changed a lot of things which violate our terms of service or other safeguards.
1 Like