When you Publish your process publish it in Orchestrator Personal Workspace Feed. after that in the assistant you will be able to see the process which you have uploaded.
@Paul_Andrei_Turcu Hi, You need to publish your studio process to Orchestrator Personal Workspace feed and the published package will be displayed in the Orchestrator My workspace in packages folder.
Then you need to create the process with the published package. Then the process will be displayed in the UiPath Assistant.
I have many folders created on the tenant where I have published all my projects before and all of them were displayed in the assistant. How comes now I can only use 1 folder?
@Paul_Andrei_Turcu You can have many folders created in the Tenant. In that case, if you want to run the process from the particular folder in orchestrator, then you can publish into Orchestrator Tenant process feed. Then the package will be displayed in the Default tenant. Then you can create the process in the required folder by selecting the package.
Also check whether the tenant is connected properly to the assistant with Proper organization.
Try logging out from UiPath assistant and reconnect.
When you publish your process to Orchestrator Personal Workspace Feed it will display in your assistant. If you want to run from a specified folder. Click on that specified folder under Processes click Add process and add the process you want to add. It will get added.
Dude I ve done this 1000 times already, I have planty of packages published to tenant and many processes on many folders created and yet for any reason all of them are gone from Assistant and I cannot runt hem attended
So I have signed out as machine key and logged in as ClientID and same results, all processes kinda loaf on assistant for 1 sec and then it vanishes and only ones from my workspace are visible.
Ensure that the automations you expect to see in the Assistant have been successfully deployed to the machine where you are running the Assistant. Check the deployment status in Orchestrator and verify that the correct version of the automation has been published to the correct environment and machine.
If itβs not help try reinstalling the assistant.