Failed runs missing from the job-specific log page

[taz-il]

• I have searched open and closed issues for duplicates.
• I have searched the forum for related topics.

---

Environment info

• Duplicati version: 2.0.6.3_beta_2021-06-17
• Operating system: Win 11 Pro, 22H2
• Backend: FTP

Description

When a backup job fails, the failures only appear on the general server page (the one for all backups), and not on the log page of the individual backup job that failed. As an example, I have this job running daily. It failed consecutively on Oct 1, 2, 3, etc, but these failures don't show up (is it only for me? is this the intended behavior for some reason?)

Steps to reproduce

This happens with every backup failure, so in order to reproduce, just cause a backup to fail (e.g. wrong user/pass for FTP; or any other way).

• Actual result:
  
• Expected result:
  

Expected: all backup attempts show up in the log (not only the successful ones), with a minimum of "Backup failed" title, ideally with some short description of the error (e.g. "host unreachable"), but this latter part is of course lower prio.

[ts678]

This sounds like Combine logs in GUI #1152. Sounds undesired and unintended but due to unstated technical reasons.
My usual guess (not confirmed by anybody knowing code well) is that the job logs (see Complete log) are results like:

duplicati/Duplicati/Library/Interface/ResultInterfaces.cs

Line 122 in 666b228

public interface IBackupResults : IBasicResults, IBackendStatsticsReporter

duplicati/Duplicati/Library/Interface/ResultInterfaces.cs

Line 32 in 666b228

public interface IBasicResults

The database LogData table looks like a backup actually writes the results when it has them -- unless it errors out early.

duplicati/Duplicati/Library/Main/Operation/BackupHandler.cs

Line 572 in 666b228

m_database.WriteResults();

duplicati/Duplicati/Library/Main/Database/LocalDatabase.cs

Line 1434 in 666b228

public void WriteResults()

duplicati/Duplicati/Library/Main/Database/LocalDatabase.cs

Line 358 in 666b228

public void LogMessage(string type, string message, Exception exception, System.Data.IDbTransaction transaction)

Even though the log is structured data, I don't know why there couldn't be a version with a little error info and no more.
Possibly it has to do with how the exceptions flow. If anyone does C# and would like to look, take the above as starters...
I would definitely love to see this improved, but somebody needs to volunteer, and volunteers are extremely scarce now.

[duplicatibot]

This issue has been mentioned on Duplicati. There might be relevant details there:

https://forum.duplicati.com/t/improve-result-reporting/16407/17

[duplicatibot]

This issue has been mentioned on Duplicati. There might be relevant details there:

https://forum.duplicati.com/t/only-restores-empty-folders/17153/7