80.2 Error Log
80.2.1 Overview ¶
The error log is a second record, separate from the processing log. It captures technical errors from program operation - code exceptions, failed connections, corrupt files, conditions that lead to a notification display. Unlike the processing log (which has one entry per email), the error log contains technical program logs, independent of individual emails.
Split into four application components, a separate log file is kept per component:
- Main - UI application
- Watcher - service watchdog
- Processor - processing engine (in service mode)
- PostProcessor - downstream tasks (e.g. ZIP, mapping resolver)
This way problems of a single component can be isolated, without searching for the source in a mixed log.
80.2.2 Storage location ¶
The log files reside in the AppData directory:
%APPDATA%\AutomaticEmailProcessor\ErrorLog_Main.json
%APPDATA%\AutomaticEmailProcessor\ErrorLog_Watcher.json
%APPDATA%\AutomaticEmailProcessor\ErrorLog_Processor.json
%APPDATA%\AutomaticEmailProcessor\ErrorLog_PostProcessor.json
In service mode the Watcher and Processor files reside in the AppData of the service account, not of the UI user.
80.2.3 Accessing the error log ¶
The error log is stored as a JSON file in the AppData directory (see 80.2.2). There is no display dialog directly in the UI - instead, two functions are available in the main menu -> More:
| Menu item |
Effect |
| Create error report… |
Bundles the error logs of all components together with system and version information into a single file on the desktop. Useful for support requests |
| Clear error logs |
Deletes the error logs (all components). Processing logs remain untouched |
If you want to see the raw content, open the JSON file directly from the AppData directory (main menu -> More -> Open application data folder…).
Note: The error report may contain personal content (profile names, account addresses) - review before sending.
80.2.4 Retention ¶
The error log keeps entries for 7 days. On program start or with each new entry, older entries are automatically removed. The period is not configurable - one week is typically enough to diagnose current problems.
If you want to archive longer, copy the JSON file manually or include it via the regular backup function.