# Search Indexer Delays

- Provider: [Close](https://down.guide/close)
- Level: confirmed
- Impact: Degraded
- lasted 46m
- started 2024-11-04 08:45 UTC
- Application UI, Indexing, API +1
- id: DWN-e4bd25e549
- Official page: https://stspg.io/g00jy1t9q3gw

## Updates from Close
### 2024-11-04 08:45 UTC: investigating
We are investigating an issue where our Search Indexer's ingestion of new events is delayed. This may result in the latest changes not being reflected on many pages across the application – Leads Search, Contacts Search, Inbox, Opportunities, Reporting, etc.

### 2024-11-04 09:20 UTC: identified
We have identified a problem with one of our search databases and have initiated a failover.

### 2024-11-04 09:29 UTC: monitoring
The failover succeeded. The Indexer is still catching up with the backlog of events. We are monitoring the situation and estimate that everything will be back to normal within 3-5 minutes.

### 2024-11-04 09:31 UTC: resolved
The issue is resolved now.

### 2024-11-07 15:06 UTC: postmortem
Close sincerely apologizes for the interruption of our service. We take the stability of our platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. 
## Impact
For some clients changes performed in Close took longer than usual to be reflected in our search functionality on November 4th from 8:06 to 9:31 UTC.
## Root Cause and Resolution
We are in the process of moving data to a new search infrastructure. Due to encountering a number of unexpectedly large objects during this process the indexing of new changes got delayed. We adjusted the indexing process to truncate the overly large objects to avoid encountering this in the future.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).