How to schedule a Studio Web project for recurring execution — is Cloud Robot with Orchestrator enough?

Hi everyone,

I’ve built an automation project using UiPath Studio Web and published it successfully. Now I want to run it on a recurring schedule (not manually).

I have a couple of questions:

  1. After publishing the project, is it correct to just create a time-based trigger in Orchestrator and set the execution target to Cloud Robot? Is that the recommended way?
  2. I noticed there’s an option to define a time-based trigger within Studio Web. If I configure that, do I still need to manually set up a trigger again in Orchestrator, or will it work automatically?

I’d really appreciate clarification on the best practice for scheduling Studio Web automations.

Thanks!

Hi @mkt.scott4

If you have time trigger in studio web project when you publish it will automatically created time trigger in orchestrator. Time trigger will help you to run process automatically certain time period or intervals. Thanks

Regards,
Kirankumar.

1 Like

@mkt.scott4

Studio web time trigger creates a time trigger in personal workspace ..

If you want automation to run from any specific folder then create a trigger in that specific folder you need

Cheers

1 Like

@kirankumar.mahanthi1 @Anil_G Thank you, that’s very helpful.

So when I set a time trigger, it’s automatically reflected in Orchestrator as well—good to know.

I published the project to My Workspace, and as expected, it appeared there.
However, when I publish it to the Tenant Processes Feed, I’m not sure which modern folder it gets reflected in.
Could you please let me know where it appears?

@mkt.scott4

For that you need to screate the time trigger..as the auto time trigger works only in personl folder ..

Please refer to screenshot

Cheers

1 Like

Hi @mkt.scott4

  1. After publishing from Studio Web, create a time-based trigger in Orchestrator and set the execution target to Cloud Robot for unattended runs.
  2. The Time Trigger activity in Studio Web is for controlling logic inside the workflow, not for actual scheduling.
  3. You still need to manually create a trigger in Orchestrator for recurring runs.
  4. Best practice is to always use Orchestrator triggers for scheduling automations.

If you found helpful please mark as a solution. Thanks
Happy Automation with UiPath

1 Like

Hi @mkt.scott4

whenever you publish process under orchestrator tenant process feed it will go to Packages section under tenant in your cloud orchestrator. as your wish you can go to any one of the modern folder yours and create process and select the package which you published to tenant so that the newly created process will be available in that specific modern folder. thanks

Regards,
Kirankumar.

1 Like

I see, so the Time Trigger activity is actually a different thing from the Time Trigger in Orchestrator. That makes sense now.

I also understand that the best practice is to trigger the process from Orchestrator, not from within the workflow itself.

Thank you so much for the clarification!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.