Maintenance request form in RPA Hub

  • Release version: Zurich
  • Updated July 31, 2025
  • 1 minute to read

    • Use the Maintenance request form to track the status of the scheduled maintenance (SM) days on the robot calendar. After a scheduled maintenance event card is accepted or rejected on the robot calendar by an RPA release manager or an admin, then a maintenance request is created for tracking.

    Table 1. Maintenance request form
    Field Description
    Number Auto-generated number of the maintenance request.
    Change request Associated change request.
    Planned Start Date Planned start date and time of the scheduled maintenance.
    Planned End Date Planned end date and time of the scheduled maintenance.
    State State of the maintenance request:
    • Pending - An MR is created when you accept the associated SM event card.
    • In Progress - When the planned start date begins, the MR is executed. The life cycle stage status of the configuration item (robot or bot process) moves to In Maintenance state.
    • Complete - When the MR completes execution of the configuration item (robot or bot process). When the associated CR is closed, then the life cycle stage status of the Configuration Item (CI) moves to Published state.
    • Canceled - When an MR is canceled. For more information about canceling an MR, see Scheduled maintenance days in RPA Hub and Manage scheduled maintenance days in RPA Hub.
    • Failed - When a CI (robot or bot process) fails due to any issue.

      When the system tries to update the CI to either in Published or In Maintenance, but unable to update. Then the MR fails.

    • Rejected - When you reject the associated SM event card.
    Configuration Item Name of the associated bot process or robot.
    Class Type of the configuration item. For example, bot process or robot.
    Note:
    Maintenance Request (MR) is unique for Change Request (CR), except for Canceled and Failed states.