Synchronization Troubleshooting app - Are errors automatically deleted?

Support - Assistance technique
1

Thanks a lot for developing the “Synchronization Troubleshooting” app which will be extremely helpful in analysing synchronisation problems.
Yesterday I saw many dozen of errors but today only one (recent) error remains.
It seems that once you “open” a specific error it disappears from the interface and cannot be viewed again. Or are errors automatically deleted after a certain period of time (24 hours?) Is that intentional? Or is there a setting somewhere which determines how long the errors are maintained for analysis.
Thanks for your advice!

2

Hi!
I will wait for @dhis2-android for confirmation, but yes, I think the errors that appear in the app are only for the past 24 hours at a time.

I think if you want to check back for older posts, you can use the API request: [your_instance]/api/jobConfigurations/errors . If you don’t have the authority to access it, it will show you which authority you are missing.

Please give it a try, does it show the errors you were looking for?

Thanks!

3

Hi Gassim

Thanks a lot for the quick answer and the explanation.

The api you shared works perfectly but also only displays the errors visible in the Troubleshooting Synchronisation app (shows the last four but not the several dozens appearing during the last days).

4

That’s interesting! Maybe there’s a backend configuration to set for how long the logs should be stored. I think the limit is not to clog the disk space.

It’s possible that errors will keep showing up until fixed though? Is there a specific issue you’re experiencing?

Thanks!

vgarciabnz (Victor Garcia) 5

Errors are deleted in the backend after 24h, that’s intentional. The Synchronization Troubleshooting app just displays what is coming from the backend.

The cleanup period is defined in the SystemSettings and it is the same period for all the jobs that just run once (such as a data import). It is possible to modify this value using the API. It might lead to larger storage in the DB for that period though.

Check the value at:

GET /api/systemSettings/jobsCleanupAfterMinutes

Modify the value with:

POST /api/systemSettings/jobsCleanupAfterMinutes?value=<value_in_minutes>
3 Likes
6

Hi Victor

Thanks a lot for the swift and concise answser. I suggest to add this information to the online user documentation.

Thanks!

7

Thank you for the suggestion. The documentation has now been updated to include this information for future reference.