Cornerstone Status
Edge Import and Feed Issue for UK/Met

Started

Resolved

Duration

57 minutes

Postmortemmajor impactVendor link

Update timeline

Resolved

This incident has been resolved.

Monitoring

A fix has been implemented and we are monitoring the results.

Identified

The issue has been identified and a fix is being implemented.

Investigating

Engineering team is analyzing the root cause of the Imports and Feeds incident.

Postmortem—

**Incident Summary** On September 18th users in the UK , MetPol Production and Pilot environments experienced issues accessing the **Imports and Feeds** functionality. **Impact** Affected users were unable to access and manage Imports and Feeds during the incident window, resulting in disruption to the affected functionality. **Root Cause Analysis \(RCA\)** The incident occurred during a planned maintenance activity. As part of the maintenance activity, changes were performed on an active host supporting the Imports and Feeds functionality. The activity required a restart of supporting services; however, the restart did not complete as expected for the dependent application workload. As a result, a supporting service did not recover as expected, which caused the dependent Imports and Feeds functionality to become temporarily unavailable. **Resolution** The affected supporting services were restored to a healthy state and the required recovery activities were completed. Following recovery, the dependent services were validated and the Imports and Feeds functionality was tested to confirm that access and normal operation had been restored. **Preventive Measures** * Controlled service restart and recovery steps will be incorporated into the maintenance activity to ensure dependent workloads are gracefully handled before supporting components are restarted. * Post validation will be strengthened to confirm that all dependent services and application functionality have fully recovered before the activity is considered complete.

Edge Import and Feed Issue for UK/Met — Cornerstone Incident Timeline & Status — DevHelm