# Kopia UI stuck in error loop when repository unavailable

**URL:** <https://kopia.discourse.group/t/kopia-ui-stuck-in-error-loop-when-repository-unavailable/849>\
**Category:** Support\
**Created:** [January 7, 2022, 12:28am UTC](https://kopia.discourse.group/t/kopia-ui-stuck-in-error-loop-when-repository-unavailable/849 "2022-01-07T00:28:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@martin](https://kopia.discourse.group/u/martin)\
**Post date:** [January 7, 2022, 12:28am UTC](https://kopia.discourse.group/t/kopia-ui-stuck-in-error-loop-when-repository-unavailable/849/1 "2022-01-07T00:28:28Z")

</div>

I used Kopia UI (0.9.8) to create a repository on an external hard drive. After the first snapshot was complete I disconnected the drive. When I later opened Kopia UI I could see that it was repeatedly trying to perform maintenance on the now unavailable repo, and looking at the log file it was generating the following message about _1300 times per second_. Yes, per second!

```auto
[2022-01-07 01:11:18.985] [info] ERROR unable to run maintenance: error updating maintenance schedule: cannot create temporary file: cannot create directory: mkdir E:: The system cannot find the path specified.

```

Since I have other repositories connected, shutting down Kopia UI wasn’t a solution, and I ended up having to disconnect the external drive repository.

Would it be possible to make Kopia not go mad when a repository is unavailable, so that I don’t have to manually connect to it every time I want to do a snapshot?

---

<div class="post-metadata">

**Author:** ![stpr](https://avatars.discourse-cdn.com/v4/letter/s/b3f665/32.png) [@stpr](https://kopia.discourse.group/u/stpr)\
**Post date:** [January 8, 2022, 3:01pm UTC](https://kopia.discourse.group/t/kopia-ui-stuck-in-error-loop-when-repository-unavailable/849/2 "2022-01-08T15:01:08Z")

</div>

I think you should perhaps file a [GitHub issue](https://github.com/kopia/kopia/issues), it is indeed bad that kopia is trying 1000+ times a second and it might be a genuine bug.

---

<div class="post-metadata">

**Author:** ![jkowalski](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/jkowalski/32/3_2.png) [@jkowalski](https://kopia.discourse.group/u/jkowalski)\
**Post date:** [January 9, 2022, 8:08pm UTC](https://kopia.discourse.group/t/kopia-ui-stuck-in-error-loop-when-repository-unavailable/849/3 "2022-01-09T20:08:44Z")

</div>

Yes, definitely file an issue, currently handling sporadically connected repositories is not really great, but we can and should improve this.

---

<div class="post-metadata">

**Author:** ![martin](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@martin](https://kopia.discourse.group/u/martin)\
**Post date:** [January 10, 2022, 6:13pm UTC](https://kopia.discourse.group/t/kopia-ui-stuck-in-error-loop-when-repository-unavailable/849/4 "2022-01-10T18:13:51Z")

</div>

Alright, I [filed an issue](https://github.com/kopia/kopia/issues/1652)!