I created a process from web studio that is supposed to be triggered by a new queue item so on the main workflow, I have the trigger set to “New Item Added to Queue” and it is configured to my target queue. but after I packaged it and is now trying to create a process, the package requirement asks me to provide a queue trigger, but if I create a queue trigger, it then requires me a package. im stuck in this circular reference
If I am understanding your request correctly, can you do the following in this order rather:
- Publish the automation from Studio Web
- Go to UiPath Orchestrator
- Create a Process
- Select the package that you just published
- Don’t worry about queue trigger here
- Once the process exists:
- Add the new queue trigger
- Select the queue and then the process which should now be available
Should help
Hi @Ezekiel_Gomez1,
- Triggers created at design-time in Studio are the only trigger types that Orchestrator validates as package requirements. They only work when they are added at process-creation time, from the Package Requirements page. So, you can avoid configuring here and create a Queue trigger with the package.
Thanks!
it wont allow me to create the process.the create button is greyed out.
if I try to create the trigger from here, it will say, “pending creation”
then on the next page, the “package requirements” is on red and the create button is still greyed out.
If I try to create the trigger first, it will ask me for the process and will get to this point again. what am I doing wrong?
I had the same issue yesterday, where I was unable to publish for a similar reason, I thought I was facing the challenge due to the trigger not being able to be made due to lack of licences, as I was on my development tenant. Let me try on Acceptance later, where I have licences, and see if I can get any publishing, otherwise I can confirm the same bug and will try to raise it as indeed the queue item trigger does seem to be blocking.
this I am working on is a POC so I was making it on a community version orch and studio. hope you keep me updated
Thats against the terms for Community Licence.
Its strictly for non-commercial purposes, and a POC is clearly a commercial purpose / value.
You can use the enterprise trial to try to use features you dont have access to, but Community is not appropriate for a POC based on the user licence agreement.
I’ve done some testing and its quite hard to workaround but I was able to publish.
Here are the current steps to get it fixed:
- Make a Commit of your current code.
- Make a new workflow with just a log message in, make it the Main
- Deleted the previous Main
- Publish as a pre-release / alpha version
You can now add the process, with the entry point wrong, and not get the validation error cause we no longer have the trigger.
- Add the Trigger manually connected to the queue you want.
- Back in studio, revert the changes to the last commit, restoring the Main and removing the dummy Main we made.
- Publish again
- In the Orchestrator you can now upgrade / rollback the project to the version that has the Main with the Queue Trigger.
The validation will now work because the chicken and egg problem is solved as the queue already exists.
Once you have done this, to avoid repeating this steps on another tenant for this process such as moving from a Developer>Test>Prod tenant you can create a Solution in the Orchestrator containing the published process, queue and trigger.
The Solution Package you make will then be able to be uploaded in another tenant and bypass the queue issue and publish correctly without any further workarounds.
I tried adding the process to a solution in Studio before publishing to see if I can get to this step without the dummy main workaround, but that doesn’t currently work on the LTS version, I dunno about the STS version as I know they did some recent updates for Solutions.
This has been an issue tha is open
What you need to do is create the connected ftrigger from package requirement itself and then cancel and start creating process a fresh..as the connected trigger is already created it links and package requirement will turn normal
..his is a workaround we use even now
Cheers
I just tried replicating this, I cannot get it to work and let me publish the process. Can you provide more details? Maybe I am doing something wrong?
Are you doing from studio web or desktop?
if studio web by default it goes to solutions and if youd eploy it automatically creates the queue trigger as well
or if you select the process individually..you would start add process select package and in package requirements click on plus to add the trigger it takes you to trigger page
create trigger most of the times if you create a new asset or new trigger package requirements would still show red(unless sometimes it does turn to normal also) …then just cancel and start add process again this time as trigger is already created you can select the trigger and it should turn normal
one thing if same queue is already associated with another process then it might fail as well
cheers
Desktop, the package was built there and published to the Orchestrator. Trying to publish it from there doesn’t work.
The solutions wrapper seems to get around this, but apparently has some issues in Studio web too if I understand you well.
Can you share more details of the steps to complete Anil? I must be doing a step wrong when I try as I cannot get past the package requirements thing when adding the package as it doesn’t seem to accept me making the trigger?
The way I do it is below (doesn’t create any such problem for me).
-
create and publish the process as I would any other process without a queue trigger. No trigger included in the code side(from studio)
-
then create the queue trigger from orchestrator and select my process that should run as soon as items are added to queue.