Question/Problem
When deploying a solution created in Studio Web to a different tenant or environment, the deployment fails for the solution package containing the Context Grounding index.
Error
Resource version 'ecs.uipath.com/v2' is not enabled for this tenant. |
|---|
Root Cause
The failure was caused by the presence of references to old Context Grounding indexes or Context Grounding related resources within the solution package.
ecs.uipath.com/v2 indicates resources related to UiPath’s Context Grounding, also known as Enterprise Context Service or ECS. Even if Context Grounding itself is available in the target tenant and indexes can be created and referenced, the continued existence of old index references in the package during deployment may still trigger the same error.
Removing the old index and creating a new index manually will not resolve the issue if the solution package still contains references to the old index; the creation or linking of that resource will be executed again during deployment.
Solution
After replacing the index with a new Context Grounding index in Studio Web, the old index may still appear in the resource list on the solution deployment screen, causing an error when it attempts to handle the old index or Context Grounding related resources during the deployment.
Please confirm the following, remove old index references, or replace them with the new Context Grounding index, then re-publish the solution package and redeploy using the latest version:
-
Ensure that Context Grounding is available in the target tenant.
-
Ensure that the creation and referencing of Context Grounding indexes are possible in the target tenant.
-
Check in the Orchestrator solution deployment screen whether any old indexes are listed in the resource list.
-
In Studio Web, check for any references to the old index in agents, apps, or processes other than the intended agent.
-
If old index references remain, remove them or replace them with the new Context Grounding index.
-
If using a storage bucket as the data source for Context Grounding, ensure that the intended storage bucket exists in the target folder of the Orchestrator deployment and that the referenced files are stored there.
-
If necessary, confirm that the storage bucket resource on the solution deployment screen links to an existing bucket in the target folder.
-
After making corrections, re-publish the solution package.
-
Redeploy using the latest version of the solution package.
If the old index continues to appear in the deployment screen after republishing, it may indicate that old index references remain in other components of the solution; please check the reference settings for all components included in the solution.