OpenText incident
Desktop Messaging BMS was experiencing failures in processing PDF files
OpenText experienced a minor incident on October 16, 2026 affecting Desktop Messaging BMS, lasting 5h 7m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 16, 2026, 09:08 PM UTC
Desktop Messaging BMS is currently experiencing failures in processing PDF files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4019383
- investigating Oct 16, 2026, 10:00 PM UTC
Desktop Messaging BMS is currently experiencing failures in processing PDF files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4019383
- investigating Oct 16, 2026, 10:48 PM UTC
Desktop Messaging BMS is currently experiencing failures in processing PDF files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4019383
- investigating Oct 16, 2026, 11:48 PM UTC
Desktop Messaging BMS is currently experiencing delays in processing PDF files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4019383
- investigating Oct 17, 2026, 12:48 AM UTC
Desktop Messaging BMS is currently experiencing delays in processing PDF files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4019383
- investigating Oct 17, 2026, 01:39 AM UTC
Desktop Messaging BMS is currently experiencing delays in processing PDF files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4019383
- resolved Oct 17, 2026, 02:16 AM UTC
Desktop Messaging BMS was experiencing delays in processing PDF files. The issue is now resolved. We appreciate your patience. Tracking Number: IM4019383