Troubleshooting
Problem
Preventive Maintenance schedules are not auto‑generated across configured frequencies, requiring manual intervention despite similar configurations.
Symptom
Preventive Maintenance (PM) schedules do not auto‑generate consistently across configured frequencies. While some PMs are created as expected, others fail to generate and require manual execution using the Generate Work action. The behavior can be observed across daily, weekly, monthly, and annual PM schedules, with higher visibility in more frequent schedules due to their recurrence. The issue occurs without any identifiable configuration differences between PMs that generate successfully and those that do not. The problem is observed generally in a multi-server setup with both application and process servers.
Cause
The issue was caused by a technical fault where the process server required a restart to resolve the failure in auto-generating PMs.
Diagnosing The Problem
- Verify the overall system health to confirm there are no underlying infrastructure‑level issues impacting background processing.
- Collect and review relevant application and process server logs to identify any errors or anomalies during PM auto‑generation.
- Confirm whether the behavior is consistent across PM schedules, noting if some PMs generate successfully while others do not under similar conditions.
- Review error and system logs carefully; if logs are verbose or noisy, enable targeted debug logging around PM generation for clearer visibility.
- Check workflow execution status to ensure there is no backlog or delay in workflow queues that could prevent PM creation.
- Review workflow agent configuration, including thread and execution settings, to ensure sufficient capacity for scheduled processing.
- Validate database health and performance to rule out latency or resource constraints affecting PM generation.
- Review PM configurations to confirm consistency across schedules and verify that no unintended changes exist.
- Perform a manual PM generation test using Generate Work to confirm that workflows and processing logic execute as expected.
- If required, restart the process server to refresh workflow execution and background task handling, then monitor whether PM auto‑generation resumes normally.
- Capture debug‑level logs during the PM generation window for further analysis if the issue persists.
Resolving The Problem
Restart the IBM TRIRIGA process server to restore normal background processing and workflow execution. After the process server restart, monitor Preventive Maintenance schedules to confirm that PMs resume auto‑generation as expected across configured frequencies. No application configuration changes are required when the issue is caused by a transient process server fault.
Document Location
Worldwide
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSAC7ZF","label":"IBM Facilities and Real Estate Management on Cloud Flex (TRIRIGA)"},"ARM Category":[],"ARM Case Number":"TS021600494","Line of Business":{"code":"LOB77","label":"Automation Platform"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSFDAS","label":"IBM Facilities and Real Estate Management on Cloud (TRIRIGA)"},"ARM Category":[],"ARM Case Number":"TS021600494","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Product Synonym
Facilities and Real Estate Management on Cloud Flex (TRIRIGA);TRIRIGA SaaS
Was this topic helpful?
Document Information
Modified date:
31 March 2026
UID
ibm17268187