Custom Field Event Interruption

What to do

• Check whether you use Close in us. 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 0m it lasted.

  Anything that failed between 2025-04-22 14:30 UTC and 2025-04-22 14:30 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 2

1. resolvedApr 22, 2025, 2:30 PM UTC

   This incident has been resolved.

   provider

2. postmortemApr 28, 2025, 5:56 PM UTC

   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 Between April 22nd 14:25 UTC and April 23rd 8:50 UTC our search functionality operated on outdated data for some users, which resulted in potentially incorrect search results. In addition, some webhooks with custom field updates were not delivered. No data was lost during the incident. ## Root Cause and Resolution A software update introduced a bug, where some events for custom field updates were malformed. As a result, the changes to custom fields weren’t reflected in search, and webhooks for these events were not sent. Close Engineering reverted the change, and reindexed all affected leads. We are adding guardrails which will prevent us from sending such malformed events in future. ## Timeline * 22 April 14:25 UTC - A software update is deployed that sends malformed events for some Custom Field updates * 22 April 21:20 UTC - Close Engineering is notified of leads not populating correctly in smart views * 23 April 04:36 UTC - Root cause is identified * 23 April 05:49 UTC - Measures applied to stop further impact * 23 April 08:46 UTC - Completed reindexing of affected leads

   provider

Corrections

None so far.

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