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.
Posted Oct 28, 2025 - 06:41 PDT
Monitoring
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.
Posted Oct 28, 2025 - 05:02 PDT
Update
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.
Posted Oct 28, 2025 - 02:26 PDT
Update
We are continuing to closely monitor activity to ensure the backlog fully clears. We will share regular updates until the queues have fully cleared.
Posted Oct 27, 2025 - 22:32 PDT
Update
We are continuing to closely monitor activity to ensure the backlog fully clears. We will share regular updates until the queues have fully cleared.
Posted Oct 27, 2025 - 20:02 PDT
Update
Our engineering team continues to monitor as the backlog clears. We'll share regular updates as things process.
Posted Oct 27, 2025 - 17:59 PDT
Update
Our engineering team continues to monitor as the backlog clears. We'll share regular updates as things process
Posted Oct 27, 2025 - 16:08 PDT
Update
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.
Posted Oct 27, 2025 - 14:05 PDT
Update
We are continuing to closely monitoring activity to ensure the backlog fully clears. We will share regular updates until the queues have fully cleared.
Posted Oct 27, 2025 - 11:08 PDT
Update
Our teams continue to closely monitor the ongoing loads. Please note that new files and scheduled feed runs should process as expected.
Posted Oct 27, 2025 - 09:00 PDT
Identified
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.
Posted Oct 27, 2025 - 05:52 PDT
This incident affected: JP SL1 (AWS) (Response Time), US SL3 (AWS) (Response Time), US SL5 (AWS) (Response Time), LAX-SL4 (Response Time), US SL4 (AWS) (Response Time), AU SL1 (AWS) (Response Time), UK SL1 (AWS) (Response Time), FRA SL1 (AWS) (Response Time), CDG SL1 (AWS) (Response Time), CDG SL4 (AWS) (Response Time), UK SL2 (AWS) (Response Time), UK SL3 (AWS) (Response Time), UK SL4 (AWS) (Response Time), US SL1 (AWS) (Response Time), and US SL2 (AWS) (Response Time).