Duration: 2 hours (7:00 AM - 8:56 AM MST)
Affected Services: MDDHCD HFA application
Status: Resolved
Executive Summary
On March 30, 2026, MDDHCD users experienced an inability to log into the HFA application due to an incorrect database version that had been restored to the Production environment following a data migration on March 27, 2026. The issue was identified, escalated, and resolved within approximately 46 minutes of IT engagement, with full service restoration at 8:56 AM MDT.
Incident Timeline
| Time (MDT) | Event |
|---|---|
| 7:00 AM | MDDHCD submits support request reporting inability to log into the HFA application. |
| 7:30 AM | Customer Success reviews the support request and begins investigating. Initial testing shows no login issues from the ProLink Solutions side; no immediate cause identified. |
| 8:10 AM | Customer Success escalates the issue to IT. |
| 8:18 AM | IT investigates and identifies a potential connection to previously approved afterhours database work performed on March 27th. Developer resources are immediately engaged. |
| 8:34 AM | Root cause is confirmed. Work on a resolution begins. The status page is updated to reflect an active extended outage. |
| 8:55 AM | A corrected database version is provided to IT and the restoration process begins. |
| 8:56 AM | Database restoration is complete. MDDHCD users regain access to the HFA application. |
| 9:03 AM | Status page is cleared following confirmed stability. Customer Success notifies MDDHCD that the issue is fully resolved. |
Impact
The outage exclusively affected MDDHCD users of the HFA application. During the incident window, affected users were unable to authenticate and log into the application. ProLink Solutions users were unaffected and experienced no disruption to service throughout the incident. This caused a delay in determining root cause.
Root Cause
The outage was caused by an incorrect version of the MDDHCD database being restored to the Production environment. This database had undergone a data migration on March 27, 2026, and the resulting version — which contained invalid or incomplete user data specific to MDDHCD — was the version provided to IT for the afterhours Production restore.
Following the March 27th restore, ProLink Solutions staff logged in and performed post-migration validation testing. Because the data integrity issue was isolated to MDDHCD user records, it was not surfaced during this internal testing, and the migration was marked as complete. The problem remained dormant until MDDHCD users attempted to log in on March 30th.
Resolution
A corrected database version was provided to IT and restored to the Production environment. Full service was restored at 8:56 AM MDT. System performance was monitored following restoration to confirm stability before the status page was cleared at 9:03 AM MDT.
Comments
0 comments
Article is closed for comments.