# Error handling

## Overview

In **Error handling** tab, you can define how the program should handle errors when they occur:

1. **Run overdue backup tasks** — if a backup fails to start for any reason, the system will automatically restart the task once the device is back online.

{% hint style="danger" %}
This function will not restart the backup plan if it's blocked by the backup window.
{% endhint %}

2. **Repeat backup on failure** — you can define the number of times a backup task should be retried in case of an error, as well as the time interval between each retry.
3. **Ignore bad sectors** — by default, the system stops the backup when bad sectors are detected. However, you can choose to ignore bad sectors and allow the backup to continue.

<figure><img src="https://319733277-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0CBTl43C3OO6ySL1DJ6k%2Fuploads%2FFuEzA7jjSOvzR9bOvDEG%2Fimage.png?alt=media&#x26;token=b4720b98-d961-4bc0-94fc-237fbdfce87b" alt=""><figcaption></figcaption></figure>

***

## Error handling for Jira&#x20;

An additional option for managing errors in **Jira** backup plans is a setting that allows you to exclude attachments from the backup process.

Enabling this option ensures that backups complete successfully even with issues involving unattached or corrupted attachments. It provides flexibility in handling minor warnings without affecting the overall backup completion status.

<figure><img src="https://319733277-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0CBTl43C3OO6ySL1DJ6k%2Fuploads%2F4HGth7uaOWGefMvHRuG3%2Fimage.png?alt=media&#x26;token=1d131d29-b532-41d5-ab41-69260461e438" alt=""><figcaption></figcaption></figure>