When cloud plugins don't load, the message now explains why and points at /reload-plugins.
What's wrong with this entry?
The message now says the session is still fetching plugins or cannot reach their marketplace, and points at /reload-plugins to see what loaded.
- Artifact reads through the session gateway gained a
relay_not_servedrefusal alongside the existing refused and unauthorized cases.
/reload-plugins shows what loaded.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Installed plugins activate in place instead of waiting for /reload-plugins
Both mention reload
-
v2.1.221
Plugin install now tells you when the plugin failed to load
Both mention reload
-
v2.1.239
Skipped-plugin warning no longer overstates what it found
Both mention reload