You can check the job log of an actual CLI-after-GUI run, to see if it uploaded anything.
They should be pretty easy to identify, assuming that GUI stats show issue of CLI stats.
Complete log will have a section like example below:
"BackendStatistics": {
"RemoteCalls": 23,
"BytesUploaded": 113793776,
"BytesDownloaded": 53430983,
"FilesUploaded": 8,
Has CLI backup done anything that impacted the GUI backup done after odd CLI result?
Has either GUI or CLI backup actually had to backup new or changed files with 2.1.0.4?
Although it might obscure an upgrade problem, note that another problem was solved by
What was running before, and on what platform? The mono precision bugs were in 2019.
was recently done, and fixes at least one case that went wrong. I don’t know if it’s this case…
If it turns out that CLI actually did something, such as create a new version or do upload, then Create bug report and sharing it via a posted link might shed some clues without a CLI run.
If nothing at all resulted (i.e. no new version made), then the database will have less to look at.
Again, the developer might have some other ideas.