Close incident

Change indexing delayed

Minor Resolved View vendor source →

Close experienced a minor incident on June 3, 2026 affecting Indexing, lasting 4h 2m. The incident has been resolved; the full update timeline is below.

Started
Jun 03, 2026, 02:50 PM UTC
Resolved
Jun 03, 2026, 06:53 PM UTC
Duration
4h 2m
Detected by Pingoru
Jun 03, 2026, 02:50 PM UTC

Affected components

Indexing

Update timeline

  1. investigating Jun 03, 2026, 02:50 PM UTC

    Changes done to CRM data are reflected in search with a delay.

  2. investigating Jun 03, 2026, 03:21 PM UTC

    We are continuing to investigate the issue.

  3. investigating Jun 03, 2026, 04:05 PM UTC

    We are continuing to investigate the issue. Updates to Close made via the web app and API may take longer than normal to appear in search results.

  4. investigating Jun 03, 2026, 04:41 PM UTC

    We are continuing to investigate the issue. Updates to Close made via the web app and API may take longer than normal to appear in search results.

  5. identified Jun 03, 2026, 05:45 PM UTC

    We have implemented a remediation for the delayed search indexing and are monitoring for improvement. Updates to Close made via the web app and API may take longer than normal to appear in search results.

  6. monitoring Jun 03, 2026, 06:17 PM UTC

    A fix has been implemented and we are monitoring the results. Updates to Close made via the web app and API may take longer than normal to appear in search results.

  7. resolved Jun 03, 2026, 06:53 PM UTC

    This incident has been resolved. The Close app and API are now functioning normally.