This is roughly the sequence of events as per the log
5710.Download.zip
This is working as designed. Canceling a download prevents "system initiated" downloads from starting until the next time the application is started. The only "user initiated" downloads are clicking the link in the available downloads notification or using the "update now" and "update resources" commands. Changing settings are not considered a "user initiated" download because it is not explicitly obvious to a user that changing that setting could immediately begin a download.
I do think the "system initiated" download block should be removed if a "user initiated" download begins, rather than needing to wait for an application restart. I'll create a case to make that change.
I do think the "system initiated" download block should be removed if a "user initiated" download begins, rather than needing to wait for an application restart.
Agreed
Changing settings are not considered a "user initiated" download because it is not explicitly obvious to a user that changing that setting could immediately begin a download.
I was expecting it in that scenario, but I'll allow that a user may want to (have time to) schedule the remaining download for a more convenient time. So it makes sense to remove the "system initiated" download block for this case!
This should be fixed in 6.3 RC2.
Confirmed i.e.
