Update – July 29, 2026 – 3:25 PM PST
Permanent Fix Deployed
OnePlan has successfully deployed the permanent corrective actions for the issue that affected the OnePlan REST and OData APIs. We have continued to monitor the environment following deployment, and API services are operating normally.
The permanent improvements include:
- Added database indexes to improve API logging database performance.
- Implemented more frequent database cleanup jobs to prevent excessive data growth.
- Expanded logging, monitoring, and automated notifications to improve visibility and accelerate detection of potential issues.
- Enhanced operational monitoring to identify performance degradation before it can impact customers.
Based on our investigation and the corrective actions implemented, we believe the underlying issue has been resolved and do not expect this issue to recur. Our engineering team will continue to closely monitor the environment to ensure ongoing stability.
Incident Summary
On July 27–28, 2026, OnePlan experienced elevated HTTP 500 errors affecting requests to the OnePlan REST and OData APIs. This resulted in intermittent failures for reports connected to the OData feed and integrations using the OnePlan REST API.
Customer Impact
During the incident, customers may have experienced:
- Reports connected to the OnePlan OData feed failing to refresh.
- Integration jobs using the OnePlan REST API failing with HTTP 500 errors.
- Intermittent connectivity or degraded performance when accessing API services.
Current Status
The OnePlan REST and OData APIs are operating normally.
Customers should now be able to successfully refresh OData reports and rerun any previously failed integration jobs. If you continue to experience issues, please contact OnePlan Support.
Root Cause
The issue was traced to the database used for API logging. Conditions within the logging database affected the performance and availability of the services supporting the OnePlan REST and OData APIs, resulting in intermittent HTTP 500 errors.
Corrective Actions Implemented
To prevent this issue from occurring again, OnePlan has implemented the following permanent improvements:
- Added database indexes to improve logging database performance.
- Increased the frequency of automated database cleanup jobs.
- Expanded application logging and diagnostic telemetry.
- Added additional monitoring and proactive alerting for API health and performance.
- Enhanced operational processes to detect and respond to similar conditions more quickly.
Our engineering team will continue to monitor the environment, but based on the implemented changes and current system performance, we believe this issue has been fully resolved.
We appreciate your patience and understanding while our teams investigated and resolved this issue.
Comments
0 comments
Please sign in to leave a comment.