Install error codes on the Capabilities screen

Symptom

• CAPABILITY_NOT_VISIBLE_TO_TENANT: This capability has not been published to this tenant.
• ALREADY_REQUESTED: this tenant has already requested capability version …
• CAPABILITY_VERSION_NOT_PUBLISHED: … is not published; a tenant may only activate what the platform released
• NO_DEPENDENCY_SET: … has declared no dependency set; …
• RUN_IN_FLIGHT: run … is …; it has not finished
• In the install steps section, next to a failed step: CAPABILITY_VERSION_NOT_PUBLISHED, CAPABILITY_NOT_VISIBLE_TO_TENANT, REQUIRED_DEPENDENCY_NOT_ACTIVE, REQUIRED_REQUIREMENT_NOT_VERIFIABLE, RESOLUTION_LOCK_NOT_LOCKED, VERIFICATION_FINGERPRINT_MISMATCH

Cause

• CAPABILITY_NOT_VISIBLE_TO_TENANT: the capability has not been published to this tenant, for example another account's capability.
• ALREADY_REQUESTED: this tenant has already requested this version; the next step is Install.
• CAPABILITY_VERSION_NOT_PUBLISHED: the version is not published; a tenant can open only what has been published.
• NO_DEPENDENCY_SET: the person who built the capability has not declared what the version needs. Such a version can be published but cannot be installed.
• RUN_IN_FLIGHT: an install for this capability is already running or was left half-finished.
• Step codes tell you the cause found while the install was running: the version is no longer published or no longer visible to this tenant (validate-config); a required dependency is not installed in this tenant, depends on a requirement that cannot be verified, or the resolution lock is no longer locked (resolve-dependency); the active pointer does not match the resolution lock (verify-activation).

Fix

1. For ALREADY_REQUESTED, press Install on the row.
2. For NO_DEPENDENCY_SET, let the capability's builder know: in the studio of the capability's owner (Capability Studio or Account Studio), Declare no dependencies is needed next to the version. Then press Install again.
3. For RUN_IN_FLIGHT, wait for the previous install to finish; a daily scheduled job resumes an install that was left half-finished.
4. For REQUIRED_DEPENDENCY_NOT_ACTIVE, first install the capability named next to the step in this tenant, then press Install again.
5. For the publish or visibility codes, ask the builder whether the version has been published and in which account it was built.