# Maintenances

## **Scheduled maintenance**

Scheduled maintenance is the easiest way to inform your customers who use your product that you are unavailable for a certain period of time due to maintenance work. This way, your customers can prepare themselves to reduce or mitigate the impact on their end.

Moreover, it is also the most effective way to be monitored by the team members who will take part in the study and other units that need to be informed about the maintenance work process.

The maintenance feature, which is very simple to manage in terms of UX and UI, is very advantageous in gaining user habits thanks to its similar structure with incident workflow.

### **To create a new scheduled maintenance:**

1. Click **Incidents** from the left sidebar.
2. Click the **Maintenance** tab.
3. Click **Create New Maintenance**.
4. Fill out required fields including the maintenance **name** & **message**, **date/time/duration** of the maintenance, **services affected**, **notification** options and lastly **internal/external** option.
5. Click the **Create Maintenance** button now.&#x20;

We are aware that you may not always have enough time to schedule maintenance work. For some urgent situations, it may be necessary to start maintenance work immediately. In such cases, you can create a normal incident with an impact value of maintenance under the heading "Incident".&#x20;

However, if you want to record your work under the maintenance list, you can also schedule a maintenance with the current date and time under the heading "Maintenance".

{% hint style="warning" %}
If you do not make selection for a future date/time, your maintenance record will appear under the **"Completed Maintenances"** heading in your maintenance list.&#x20;

In addition, it will automatically create **an incident** with "Maintenance" impact in "Identified" status. You can follow the maintenance process from this created incident and provide updates here.
{% endhint %}

**Let’s remember some important points:**

* If you choose maintenance as **public**, you will send notifications both your subscribers\* who have opted-in to receive notifications and your integrations\*. However, your in-house employees will only be notified through the integration\* communication channels you have configured if you choose **internal**.
* **Internal services** are reminded of you with the **lock** **icon** within the services you choose. Please note that this service information _is not shared_ in any way in the notifications sent to the audience outside the institution, including your public status page.

\*_You can find Subscriber and Integration communication channels on the left side bar._

![Create Maintenance](https://1378665539-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LuHHbbgcDhfS5tX43QU%2F-MZtR0LUWBgx9oIPVH3E%2F-MZtRBZekcKZBMGSmLIx%2FCreate_Maintenance.png?alt=media\&token=5d9a82da-45ef-4f98-9f2a-30b37c083d0e)

### **To update a scheduled maintenance:**

1. If you want to make any changes to a scheduled maintenance, click the **View** button for the relevant record from the maintenance list.
2. After making your changes on the maintenance detail page that opens, click the **Update** button below the page.

### **After creating a new maintenance, how will the process work?**

* In your maintenance list, you can also distinguish your future maintenance records from **"Completed Maintenances"** records by the **green color** on them.

![Maintenance List](https://1378665539-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LuHHbbgcDhfS5tX43QU%2F-MZtRV5l27QpFBdvaZN1%2F-MZtWzZ-hTJ57T0llsNl%2FMaintenance_List.png?alt=media\&token=7aae02be-9276-4f92-a637-e1e9cb915004)

* Immediately after the maintenance schedule is set, if you tick off the option to send a notification depending on whether maintenance is internal or public, your notifications **(reporting a new maintenance is scheduled)** will be sent instantly through integrations and subscribers communication channels.
* The above notification sending process also applies when you update in maintenance.
* If your maintenance is **public**, you can view the maintenance details under **“Future Maintenance”** heading in your public status page as below.

![](https://1378665539-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fstatusentry%2F-MZPVCkrOQye6iUkxrYj%2F-MZPVIzWY_7n0f9EpYQC%2F2.png?generation=1619647349211982\&alt=media)

### **Maintenance work begins:**

* In your maintenance list, the **green color** above your maintenance record will be _removed_ and this record will now appear under the **"Completed Maintenances"** headin&#x67;**.**
* While you were scheduling maintenance, if you ticked off the option to send a notification depending on whether maintenance is internal or public, your notifications **(reporting the start of the maintenance process)** will be sent instantly through integrations and subscribers communication channels.
* Your **public** maintenance record under the **“Future Maintenance”** heading is _automatically moved_ to the incident list on the public status page.
* **An incident** with "Maintenance impact" will be _automatically created_ under the Incident list with "Identified status" so that you can monitor the maintenance work progress. In order to distinguish this incident record from other incident records in your incidents list, we have put the maintenance key icon at the bottom right as below.

![Maintenance Key Icon in the Incident List](https://1378665539-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LuHHbbgcDhfS5tX43QU%2F-MZtXC_uhaPP-yL3lDCr%2F-MZtasR7zZ3504HqcyYG%2FMaintenance_Icon.png?alt=media\&token=5b4a0b41-1b31-4609-98cd-7515d4a43d2d)

### **Monitoring the process:**

* The incident record, which was created automatically due to scheduled maintenance, has four statuses that are the same as the normal incident statuses. Therefore, you can easily update the status of this incident record in order to monitor the maintenance work process.
* The other actions you will take during the maintenance work process are the same as the incident workflow.
* During the maintenance work; if you wish, you can also share the follow-up of the process **only** within the organization via each **new internal entry** of this incident record.
