Outage in Cornerstone

Minor Issue - Edge Import Feeds Processing Delays - All Swimlanes

Resolved Minor
October 27, 2025 - Started 4 days ago - Lasted 1 day
Official incident page

Incident Report

On October 26th we experienced an issue with Edge Import access, which has since been resolved. As a result, a backlog of pending feeds accumulated, causing delays in feed processing across all swimlanes. We are seeing feeds actively processing, and our team is proactively monitoring progress to ensure timely completion. Status Page will be updated regularly to reflect the progress.

Need to monitor Cornerstone outages?

One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.

Latest Updates ( sorted recent to last )
RESOLVED 3 days ago - at 10/28/2025 01:41PM

Our observations indicate feeds are processing as expected (see below), therefore concluding this issue as Resolved.

Following the initial issue, subsequent feed runs failed with the error “The feed was already running.” This is due to the Edge Import system’s built-in fail-safe and recovery mechanism, which prevents new feed runs from initiating while a previous instance is still in progress. This ensures the feed will become available for processing during the next scheduled or manually triggered run.
The upcoming feed run is expected to process successfully.

Summary of Current Status
- First feed run: Stalled as a result of a known infrastructure issue, which has now been resolved.
- Second feed run: Failed with the error “The feed was already running,” in accordance with the system’s fail-safe logic.
- Third feed run: Anticipated to be successful on the next attempt.

MONITORING 3 days ago - at 10/28/2025 12:02PM

Queues on all swimlanes are cleared.

Following the initial issue, subsequent feed runs failed with the error “The feed was already running.” This is due to the Edge Import system’s built-in fail-safe and recovery mechanism, which prevents new feed runs from initiating while a previous instance is still in progress. This ensures the feed will become available for processing during the next scheduled or manually triggered run.
The upcoming feed run is expected to process successfully.

Summary of Current Status
- First feed run: Stalled as a result of a known infrastructure issue, which has now been resolved.
- Second feed run: Failed with the error “The feed was already running,” in accordance with the system’s fail-safe logic.
- Third feed run: Anticipated to be successful on the next attempt.

We are actively monitoring the situation and will continue to provide updates as needed.

IDENTIFIED 3 days ago - at 10/28/2025 09:26AM

Following the initial issue, subsequent feed runs failed with the error “The feed was already running.” This is due to the Edge Import system’s built-in fail-safe and recovery mechanism, which prevents new feed runs from initiating while a previous instance is still in progress. This ensures the feed will become available for processing during the next scheduled or manually triggered run.
The upcoming feed run is expected to process successfully.

Summary of Current Status
- First feed run: Stalled as a result of a known infrastructure issue, which has now been resolved.
- Second feed run: Failed with the error “The feed was already running,” in accordance with the system’s fail-safe logic.
- Third feed run: Anticipated to be successful on the next attempt.

We are actively monitoring the situation and will continue to provide updates as needed.

IDENTIFIED 3 days ago - at 10/28/2025 05:32AM

We are continuing to closely monitor activity to ensure the backlog fully clears. We will share regular updates until the queues have fully cleared.

IDENTIFIED 3 days ago - at 10/28/2025 03:02AM

We are continuing to closely monitor activity to ensure the backlog fully clears. We will share regular updates until the queues have fully cleared.

IDENTIFIED 3 days ago - at 10/28/2025 12:59AM

Our engineering team continues to monitor as the backlog clears. We'll share regular updates as things process.

IDENTIFIED 4 days ago - at 10/27/2025 11:08PM

Our engineering team continues to monitor as the backlog clears. We'll share regular updates as things process

IDENTIFIED 4 days ago - at 10/27/2025 09:05PM

The backlog has cleared for most swimlanes. We are continuing to closely monitor progress to ensure it continues to catch up. We will share regular updates until the queues have fully cleared.

IDENTIFIED 4 days ago - at 10/27/2025 06:08PM

We are continuing to closely monitoring activity to ensure the backlog fully clears. We will share regular updates until the queues have fully cleared.

IDENTIFIED 4 days ago - at 10/27/2025 04:00PM

Our teams continue to closely monitor the ongoing loads.
Please note that new files and scheduled feed runs should process as expected.

IDENTIFIED 4 days ago - at 10/27/2025 12:52PM

On October 26th we experienced an issue with Edge Import access, which has since been resolved.
As a result, a backlog of pending feeds accumulated, causing delays in feed processing across all swimlanes.

We are seeing feeds actively processing, and our team is proactively monitoring progress to ensure timely completion.

Status Page will be updated regularly to reflect the progress.

The Status Page Aggregator Built for IT Teams

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 4522 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook