I am using both Community and Enterprise Cloud Orchestrator, and I am unable to upload my custom activity package to the Cloud Orchestrator. I am getting the error “Invalid Package Details (#1654)”.
I was able to upload the same package in my Enterprise version on 22/Jul/2026 by going to Tenant → Packages → All Packages → Upload.
However, from 30/Jul/2026 onwards, I am no longer able to upload the package, and I get the same error without any additional details.
To check whether there was an issue with my package, I created a Library using the Studio template and tried to upload it. I got the same error. I also created another sample custom activity, and I am getting the same error for that activity as well. The activities work fine in Studio, and before 22/Jul/2026 I had uploaded custom activities several times on lower environments without any issues.
I also tried uploading the package on my Community Cloud Orchestrator, but I am getting the same error there as well.
For the Enterprise version, the client opened a ticket with UiPath. According to their support team, they asked me to create a sample activity and upload it to the Tenant feed under Tenant → Libraries, instead of uploading it to the Host feed. I am able to upload the package to the Tenant feed, but I do not understand what the difference is between the Host feed and the Tenant feed, or why I am able to upload the package only to the Tenant feed and not to the Host feed.
Can someone help me understand why this is happening and what could be causing the “Invalid Package Details (#1654)” error?
Hi @Ashish_Parjapati ,
Please try with the below steps:
1.Upload custom activities to Tenant → Packages → Libraries instead of Tenant → Packages → All Packages.
2.Ensure the package is built as a Library/Custom Activity and not uploaded to a feed intended for processes.
3.If the issue started recently, it is likely due to a UiPath Cloud validation or feed behavior change rather than a problem with the package.
Hi @Ashish_Parjapati,
For now I don’t have the access, so I am not able to share the screenshot.
Based on your screenshot, the Upload option is not available under Libraries. This usually happens when:
Your user role does not have Library Create/Upload permissions.
You are connected to Automation Cloud/Orchestrator where library publishing is restricted.
The package feed is configured as read-only.
Please ask your Orchestrator administrator to verify your permissions under Manage Access → Roles and confirm that the Tenant Libraries Feed allows uploads.
As an alternative, you can publish the library from UiPath Studio directly to Orchestrator using Publish → Orchestrator Tenant Feed if you have the required permissions.
I’m an admin in the Orchestrator, and I don’t think that option was available before either. If you can guide me through where to look under the Libraries section, I can check and let you know what I find. but the custom activity is developed using Visual studio, if you can guide me on that also(how to upload it using the UiPath studio) only the custom activity.
i am using both enterprise and community version of the orch. both are cloud as i mentioned in the Question., i already shared a screenshot of Tennant->packages->Libraries.
Since you are using UiPath Automation Cloud for both Enterprise and Community and have already checked Tenant → Packages → Libraries, I would suggest checking the Tenant Feed configuration and whether the package is being published to the correct feed.
You can try:
Go to Tenant → Settings → Deployment → Packages.
Check which Libraries feed is configured/enabled.
Make sure the .nupkg is uploaded to the same tenant/feed that your Studio is connected to.
In UiPath Studio, open Manage Packages → Settings and verify that the corresponding Orchestrator feed is enabled.
Refresh the package source and search for the custom activity again.
If the package is still not visible, try logging out/in to Studio or restarting Studio after refreshing the feed.
Hope this helps. Please let me know if the package appears after checking the feed configuration.
worth pointing out first, that older Knowledge Base thread about #1654 doesnt apply to your case, its for standalone/on prem Orchestrator (IIS reset, NuGetPackages folder permissions), none of that exists in Cloud Orchestrator, so dont go down that path
on the actual question, Host feed vs Tenant feed. In a multi tenant setup, Host feed is meant to be organization wide, shared across all tenants, and is really scoped to Host level administrators, not regular tenant admins, even ones with full admin rights inside their own tenant. Tenant feed is scoped to just that one tenant’s libraries, wich is what almost everyone actually uses day to day. What you’re describing sounds like Host feed access was never really meant to be open to you, and something in the validation pipeline changed around end of July to correctly start enforcing that boundary, instead of silently letting it through like before
the pattern that convinces me its not your package or your permissions, its broken identically on two separate Cloud orgs (Enterprise and Community) with the exact same nupkg that worked fine before 22/Jul, that timing plus cross tenant consistency points to a platform side change, not something fixable on your end. Since support already gave you the working path (Tenant feed), id just standardize your publish flow to always target Tenant feed going forward and not fight the Host feed path, its very likely intentionally locked down now rather than a bug you need to work around
hope that clears up the confusion on the two feeds at least
Thanks for the explanation—it really helped. One question that came up based on your explanation and the current Orchestrator configuration: does this mean that going forward we won’t be able to upload custom activities (or “libraries” or other nuget packages ) directly under Tenant → Packages → All Packages → Upload, or under the Libraries section instead of All Packages?
There is a very simple answer, you just need to enable the tenant feed, which is not activated by default. If you dont do that only the Host feed shows, which as far as I know is managed by UiPath so you can never upload anything to it.
If you enable both host and tenant feeds you can then select the tenant feed in the Libraries section, and upload the package. Assuming the package error is because the Orchestrator is not recognizing it as a robot it can run, and the package is infact valid, the library feed should accept it.
Thanks @Jon_Smith for this, i appreciate your efforts , when the client opens a ticket with UiPath , they also suggested the same thing and it is working in the production right now, now i understand based on the support provided by UiPath that from recent update to the orchestrator we have to do the same settings that you are showing here . Once again thanks to you for valuable suggestion and help. Hope it will help other members also in the community.
