40 Processing Time Diagnostics
40.1 Overview
The Processing Time Diagnostics window provides a comprehensive overview of program activity and configured processing times. It helps with analysis and troubleshooting of time-controlled processing.
Access: Menu button → Other → Processing Time Diagnostics...
40.2 Tab: Runtime
Shows program activity for the last 7 days based on the heartbeat mechanism.
Display
| Column |
Description |
| Date |
Day of the activity period |
| Start |
Program start time |
| End |
Time of last known activity |
| Duration |
Total runtime of the activity period |
Heartbeat
The program regularly updates a timestamp (every 60 seconds). Activity periods are reconstructed from these timestamps.
Usage
- Check availability: Was the program active at certain times?
- Detect restarts: Multiple periods in one day indicate restarts
- Analyze runtime: How long did the program run in total?
40.3 Tab: Global Processing Times
Shows the global time window settings configured in program options.
Display
| Information |
Description |
| Status |
Whether global time windows are enabled |
| Weekdays |
Active processing days |
| Period |
Configured From-To time range |
| Currently Active |
Whether a time window is currently active |
| Next Window |
When the next time window begins |
Changes
Global processing times are configured in Program Options under Processing.
40.4 Tab: Profile-Specific Processing Times
Lists all profiles that have defined their own processing times (independent of global settings).
Display
| Column |
Description |
| Profile |
Profile name |
| Status |
Whether the time window is currently active |
| Schedule |
First line of the configured times |
| Files today |
Number of files successfully processed today |
Detail View
Double-clicking a profile opens the detail view with: - the complete schedule, - the status with the end of the current or the start of the next time window, - the files processed in the last 7 days with date, time and result.
Configuring Profile-Specific Times
- Open profile → General
- Enable Use profile-specific processing times
- Configure schedule (weekdays, time ranges, repetitions)
40.5 Tab: Waiting Files
Shows files waiting for their time window.
Display
| Column |
Description |
| File |
Full path to the waiting file |
| Profile |
The profile that will process the file |
| Detected At |
Time when the file was found |
| Waiting Until |
Start of the next time window |
| Remaining |
Remaining wait time |
Waiting Files Occur When:
- A file belongs to a profile whose time window is not active
- A profile with "Once per time window" has already processed in this window
Outside the global time window, the program checks only profiles with their own processing times; files of the other profiles are found again in the global time window - they do not appear here.
Actions
| Action |
Description |
| Process Now |
Process selected file immediately (ignores time window) |
| Remove from Queue |
File will not be processed |
40.6 Schedule Types
Time Range (FromTo)
Processing during a time range (e.g., 09:00-17:00): - Files are processed immediately when they appear in the time window - Unlimited processing per time window
Time Point (At)
Processing at a specific time (e.g., 09:00): - Processing only once per time window - Files that appear later wait for the next window
Catch-Up
When enabled, missed processing is caught up: - Example: Time point 09:00, Catch-up 30 minutes - If program starts at 09:15, processing still occurs - After 09:30, the time window is missed
40.7 Troubleshooting Tips
Files Are Not Being Processed
- Check global time windows: Is the current time window active? (Does not apply to profiles with their own processing times.)
- Check profile-specific times: Does the profile have its own restrictions?
- Check waiting files: Is the file waiting for a time window?
- Check runtime: Was the program active at the expected time?
Processing Does Not Occur at Expected Time
- Time point vs. time range: With "time point", only one processing per window
- Catch-up setting: Was the window possibly missed?
- Check system time: Is the computer's system time correct?
Unexpected Delays
- Other profiles: Are FileGroups blocking processing?
- Check interval: How often does the program check? (Default: 2 minutes)
- System load: Is the system overloaded?