Orchestrator server stop-start, checklist?

Hello community,

at my workplace we will need to shut down the Orchestrator server for some Azure maintenance. I’m the new RPA guy/entire team and so far never needed to do this. Besides pausing schedules and alerting stakeholders, is there are anything else server related I should take into account or note down before shutting down the server? I remember when restarting the app server for this other RPA platform (you might guess) some master key was needed to put it to run again. Things like that. Documentation from knowledge transfer is scarce.

Thanks a lot!

Hi @JMGRX,
Each enterprise customers can contact with our Technical Support :slight_smile:

Thanks for the input, Pawel. However, your response doesn’t provide the details I’m looking for regarding Orchestrator server shutdown. If you could share more relevant information on that topic, it would be more helpful. Appreciate it.