# A couple of suggestions

**URL:** <https://forum.duplicati.com/t/a-couple-of-suggestions/3255>\
**Category:** Features\
**Created:** [April 18, 2018, 1:14pm UTC](https://forum.duplicati.com/t/a-couple-of-suggestions/3255 "2018-04-18T13:14:21Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)\
**Post date:** [April 19, 2018, 3:45pm UTC](https://forum.duplicati.com/t/a-couple-of-suggestions/3255/3 "2018-04-19T15:45:14Z")

</div>

> [@adhawkins](#):
>
> Provide a means of stopping any queued jobs from operating.

I think there was a discussion about this sort of thing but I’m having trouble finding it at the moment. Using “Pause” as suggested by @TheDaveCA might do the trick, but I’m actually wondering if an update of mono while Duplicati is paused might interrupted the pause…

> [@adhawkins](#):
>
> void adding the same entry to the queue more than once.

I know this one has been discussed a few times and the issue is that the active job isn’t considered part of the queue.

I think that functionally this is kind of related to [How can I disable start of missed backups when duplicati start?](https://forum.duplicati.com/t/how-can-i-disable-start-of-missed-backups-when-duplicati-start/2090)

I’m not finding it now but I believe there are also some posts suggesting a “don’t run if it’s been less than `X time` since the last successful run” feature.

---

_[View the full topic](https://forum.duplicati.com/t/a-couple-of-suggestions/3255)._