- Level
- confirmed
- Worst impact
- Degraded
- Components
- Querying
- Down Index
- 20of 100
What to do
Check whether you use Close Querying. 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 1h 57m it lasted.
Anything that failed between 2023-08-14 18:50 UTC and 2023-08-14 20:46 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 5
- investigating
We are currently investigating an issue whereby the limit function in our search filters is not being applied to bulk actions.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- resolved
This incident has been resolved.
provider
- postmortem
Close sincerely apologizes for the interruption of our service. We take the stability of a platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. ## Impact Bulk actions performed in Close between 2023-08-14 05:36 UTC and 2023-08-14 20:16 UTC were potentially delayed, executed on too many entities, or not executed at all. If a bulk action was executed and was using the “limit” search option, said option was not observed and the bulk action was performed on all search results without limit applied. Once we uncovered the issue we cancelled the execution of queued bulk actions to prevent action being taken on unintended entities such as leads or contacts. ## Root Cause and Resolution A bug was introduced in our API that caused the “limit” parameter to be discarded when bulk actions were being performed. Upon finding the bug we deployed an updated version of our API that solved the issue. We have increased the number of test cases covering this functionality to prevent similar issues from happening again. Improvements were also put in place regarding our escalation procedures to ensure issues like these get resolved more promptly in the future. ## Timeline * 2023-08-14 05:36 UTC - A bug is introduced in our API that discards the “limit” parameter when creating bulk actions * 2023-08-14 16:13 UTC - Close Engineering becomes aware of an issue with Bulk Actions * 2023-08-14 19:49 UTC - Close Engineering deploys a change fixing the issue with Bulk Actions * 2023-08-14 20:16 UTC - Bulk actions that weren’t executed yet were paused to avoid unintended action
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d3e4697dff
Is Close still down?
No, this incident was resolved 2023-08-14 20:46 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
1h 57m, from 2023-08-14 18:50 UTC to 2023-08-14 20:46 UTC, by the times Close posted.
What was affected?
Close named Querying.
What caused it?
Close hasn't published a root cause. If it does, it shows here.
Where does this come from?
Close's official status page, https://status.close.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.