The adapter is installed andItential Platform has been restarted, but the adapter is not available inItential Platform.
Verify the installation directory. The adapter must be installed in the directory that matches its namespace. See Installation location.
Verify dependencies are installed in the adapter directory. Run npm install from inside the adapter directory, not from theItential Platform home directory. See Dependencies.
Verify the adapter lints clean. Syntax errors in particular can preventItential Platform from loading the adapter. Run npm run lint:errors from the adapter directory. See Linting.
Check theItential Platform logs. WhenItential Platform fails to load an adapter, it writes an error to the log. The log entry typically identifies the cause.
Check for namespace and pronghorn.json compatibility issues. Newer versions ofItential Platform have stricter requirements for pronghorn.json and enforce npm-compatible namespace rules (no uppercase letters). These requirements can prevent the adapter from loading and may also prevent the service instance configuration from being editable inItential Platform Admin Essentials.
Adapters built before November 2019 that have not been migrated to a newer version may fail to load on currentItential Platform releases.
If the logs do not identify the cause, contact the Itential Adapters Team with the log output.