It seems to be remembered from having been run, not just configured. After run, even if deleted, it applies to its original job and to other jobs that run, until Duplicati is restarted.
I just hit this with an intentionally invalid (from another test) hostname URL got warnings from my production backup which only sends mail at the job level. No globals either now.
Found that in 2.1.0.118, now trying 2.1.0.5 Stable, first with an error, then with right URL according to Duplicati Console. I might back down to test with an error because I can get better evidence of what’s sent in http rather than https. e.g. Wireshark showed wrong job.
Steps are something like this.
- Consider setting up a live log, server log, and Wireshark
- Create two jobs (A and B), and run them to see they run
- Go to Duplicati Console to get the config you should use
- Put it in job A with
send-http-urlexcepthttpinstead - Run job B. Runs quietly.
- Run job A. Gets warnings popup.
- Run job B. Gets warnings popup. Wireshark backup-name shows it sent job A’s data.
- Clear the
send-http-urlfrom job A. - Run job B. It’s still sending job A’s data even though job A now lacks config to send it.
- Restart Duplicati.
- Run both jobs and they are back to being quiet, but what was stuck before restarting?
EDIT 1:
I thought my Duplicati Console was past its free limits, but it did show the job names, which makes it easier than Wireshark and http cleartext to notice that job B was sending for job A.
EDIT 2:
With Duplicati Console, one can use https and not have http complaint.