A library created using the Studio Library project template is published to the tenant in Orchestrator. Despite appearing under Tenant > Packages > Libraries, it does not appear in the "All Packages" section of Studio or StudioX’s "Manage Packages" when attempting to add it as a dependency in an RPA process project. Why?
Overview
This article outlines the steps to resolve instances where a newly published library does not appear in Studio or StudioX's "Manage Packages" after being successfully published to the tenant in Orchestrator.
Troubleshooting Steps
To ensure proper visibility of the library, the following checks can be performed:
- Verify Permissions in Orchestrator
Ensure the necessary access rights to the library are provided under Tenant > Manage Access > Roles. Confirm users assigned to the Tenant Role have permission to view and use libraries.
- Validate Tenant Connection
Confirm Studio or StudioX is connected to the correct tenant where the library was published. Misconnection to a different tenant may prevent the library from appearing.
- Restart Studio
Restart Studio or StudioX after publishing the library to ensure the Package Manager reflects the most recent updates.
- Check Filters
If the library is published with the "Is Prerelease" checkbox enabled, ensure the "Include Prereleases" option is selected in Studio or StudioX's Package Manager. This filter ensures that prerelease libraries are displayed for dependency selection.
