Copy job not updating progress bar

Bug
#1

Please describe what you are doing to trigger the bug:
I’ve been backing up to an external HD for a few days, and decided to add Backblaze B2 as my offsite backup. So I created a new schedule with a COPY and CHECK job to copy from the HD to B2, which I then manually started by clicking the Play icon.

Please describe what you expect to happen (but doesn’t):
I expect the progress bar for the COPY job to show the current progress.

Please describe what actually happens (the wrong behaviour):
The progress bar remains at 0%

I can confirm that data is being uploaded, both by checking the B2 bucket and by clicking the progress bar to view the log.

Currently the log shows that the progress is 54.5%, but the AJAX request to /get_schedule_status returns 0% in the response object:

..snip..
{
	"0": {
		"schedule_index": 1,
		"job_index": 0,
		"is_running": true,
		"percentage": "0%",
		"status_code": "",
		"status_note": "",
		"log": "copy-20201221-140322.log"
	}
}
..snip..

This is with Duplicacy Web Edition 1.4.1

1 Like
#2

This will be fixed by the next release.

2 Likes
#3

Now that the COPY and CHECK have finished, the schedule still says it is in the running state. Is this related and also addressed in the next release? And more importantly, is it safe for me to stop and remove this schedule? (The copy and check are incorporated into my main schedule, this was just a one-off schedule for the initial copy).

/get_schedule_status is currently returning this response:

{
	"job_status": [
		{
			"schedule_index": 1,
			"job_index": 0,
			"is_running": false,
			"percentage": "0%",
			"status_code": "success",
			"status_note": "Completed",
			"log": "copy-20201221-140322.log"
		},
		{
			"schedule_index": 1,
			"job_index": 1,
			"is_running": false,
			"percentage": "0%",
			"status_code": "success",
			"status_note": "Checked",
			"log": "check-20201223-120905.log"
		}
	],
	"message": "ok",
	"schedule_change_id": 15,
	"schedule_status": [
		{
			"schedule_index": 0,
			"is_running": false,
			"next": "Next run in 12:48:09",
			"has_jobs": true,
			"is_paused": false
		},
		{
			"schedule_index": 1,
			"is_running": true,
			"next": "Next run in 3 days 11 hours",
			"has_jobs": true,
			"is_paused": false
		}
	]
}
#4

This can be caused by deleting another schedule when one schedule is running: Duplicacy job status still "Running" after completion

It will be fixed in the next release.