Introduction
Depending on the jobtype you may observe different behavior after an (un)planned restart of the Central Server: Running Jobs prior to the restart may afterwards show up as Unknown, or may continue finalization as usual.
Resilience per jobtype
Resilient
- SAP jobs - the SAP system will continue processing the SAP job while the Central Server is down. As soon as the Central Server is up again, the SAP agent will sync the status of the SAP job
- OS jobs - the Platform agent will continue processing the OS job while the Central Server is down. As soon as the Central Server is up again, the Platform agent will sync the status of the OS job.
Not-Resilient
- JDBC jobs - Jobs in status Running prior to the restart will afterwards show up as Unknown
- Webservice jobs - Jobs in status Running prior to the restart will afterwards show up as Unknown
Optional Resilient
- RedwoodScript jobs - these are out-of-the box not resilient, but can be made so using instructions in https://docs.runmyjobs.cloud/?latest=RsJobDefType
Applies To
This FAQ applies to all RMJ versions
Comments
0 comments
Please sign in to leave a comment.