Diagnose and fix Cartographer issues when publishing, browsing, installing, or reviewing skills: grouped by where in the flow the problem shows up.

Grouped by where you are in the flow — see Sharing skills with your team for the full procedures. The cause is often not what the on-screen message suggests.

Cause: You lack Libraries.Create, and nothing on screen says so.

Solution: You can only submit for review because you don't have publishing permissions. Ask an admin to grant you Libraries.Create — refer to Roles and permissions.

Cause: On the publishing page, the Submit for review and Publish buttons stay disabled because mandatory fields are still empty.

Solution: Set values for the mandatory publishing fields.

Cause: Your tenant's Deployment setting is Only host feed — there's no tenant feed to publish into.

Solution: An admin sets Feeds to Both host and tenant feeds and saves.

Cause: Your tenant's Deployment setting (Only host feed) shows as a checkbox instead of a dropdown on older Orchestrator versions.

Solution: An admin sets Feeds to Both host and tenant feeds and saves.

Cause: Orchestrator refused the upload itself. Your role is insufficient, whatever the button offered.

Solution: Ask the admin to fix your role. The button showing up is only a hint, not a guarantee.

Cause: Versions only ever go forward.

Solution: Raise the version number.

Cause: Usually a connection problem — the catalogue is the tenant feed.

Solution: Check for an offline banner first. If your connection is fine, ask your admin to confirm you've been granted the Libraries.View permission.

Cause: The feed couldn't be read, so Cartographer fell back to what's on disk.

Solution: Retry. Check your network and permission.

Cause: Skill and routine changes apply to new conversations only.

Solution: Start a new conversation.

Cause: Cartographer scans its skills folder at startup, and Sync skills only refreshes cloud skills.

Solution: Restart Cartographer.

Cause: This message can mean something failed on the server side during submission, not just a network problem — it covers any failure during submit, not only connectivity.

Solution: Confirm your network connection is fine, then contact your admin or UiPath Support — this can be a server-side issue, not just a connectivity problem.

Cause: That lane only renders for people who hold the publish permission.

Solution: Expected if you're a submitter, not a reviewer.

Cause: Nobody with the permission has looked at the queue yet — there's no reminder or SLA.

Solution: Chase a person directly. Make sure someone owns the queue.

Cause: No shared feed is configured for your environment.

Solution: Nothing to fix — this is expected without a shared feed.

Cause: Your organization doesn't allow installing directly from shared feeds.

Solution: Use Request to add to Orchestrator instead.