"Installed, not in effect": what each plugin state means

The Installed tab shows a short status next to every plugin. Most of the time it says it is working. This page explains the others, and what to do about each.

The states

In effect

The plugin is loaded in the running DSH. Nothing to do.

Installed, takes effect after a restart

The files are in the profile, but the running DSH loaded its plugins before they arrived. Restart dsh web or the desktop app. Many plugins avoid this by loading on the fly, which is why some installs need no restart and others do.

Installed, not compatible with this dsh

The plugin declares a DSH version range and yours is outside it. The market checks this before it installs, and shows the range it found. Update DSH, or look for a plugin release that supports your version; the market can suggest the newest compatible release for an update.

Installed, not in effect

The package is on disk, but nothing loads it. The common reasons are that it is a library another plugin depends on (shown as "dependency library"), or that it is a plain dependency that declares nothing for DSH to load. A package that an Agent preset in your own configuration mounts shows "loaded by your configuration" instead, because presets load per session rather than at startup.

If you expected it to do something, check that it is a plugin and not just a library, and whether it is switched off in the profile.

Installed, failed verification

The files are there, but the package is incomplete or has no loadable entry, often because an install was interrupted or a build step did not run. Reinstalling from the market usually fixes it.

Did not load at startup

DSH tried to load it and it failed. The host log names the error. A plugin that fails this way can be switched off from the market while you look into it.

Disabled

You, or another manager, switched it off. It stays installed and can be switched on again.