Are you looking at the same only Duplicati tab the whole time? Can you repro the issue?
It doesn’t need to be that mysterious. Can you reveal the nature of those two warnings?
That invites a similar persistence problem, if the dialog hangs around awaiting a Dismiss. Scheduled run might happen, and then what, and what if there’s an error in the next run?
One can look at “Last successful backup” on home screen – if one knows what to expect.
Duplicati Console at app.duplicati.com is probably meant to help track backup results. Developer could speak more to that, but since you care, have you considered using that?
Duplicati apparently has a designer available to help sort this sort of thing out, but I’m not certain how quickly or effectively they work. The new UI heading to release has old issue regarding nuisance alerts that need to be dismissed manually. It has not been addressed.
Regardless, this is a question for developer and/or designer. Meanwhile, give repro steps.
That’s the nature of most backup programs. They search the entire Source for changes. Generally people like backup as fast as possible. The use-background-io-priority option allows yielding drive access to other use, but then those other uses are hitting the drive.
usn-policy can sometimes help some Windows NTFS users avoid searches for changes.
I’m not sure if there’s an open request for a run-slow-to-go easy-on-my-hardware request. You can try searching the forum and GitHub Issues. There WAS a case where activity on USB stick had exceeded computer port power. Solution there was to use an external hub.