Change indexing delayed

What to do

• Check whether you use Close Indexing. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 2m it lasted.

  Anything that failed between 2026-06-03 14:50 UTC and 2026-06-03 18:53 UTC may need a replay.

• Subscribe to Close's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=close works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Close 7

1. investigatingJun 3, 2026, 2:50 PM UTC

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

   provider

2. investigatingJun 3, 2026, 3:21 PM UTC

   We are continuing to investigate the issue.

   provider

3. investigatingJun 3, 2026, 4: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.

   provider

4. investigatingJun 3, 2026, 4: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.

   provider

5. identifiedJun 3, 2026, 5: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.

   provider

6. monitoringJun 3, 2026, 6: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.

   provider

7. resolvedJun 3, 2026, 6:53 PM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.