이 사건은 해결되었습니다.
이 사건은 원 애플리케이션의 누락 된 구성으로 인해 코드 변경을 원 애플리케이션에 배포하는 데 사용됩니다. 투자 후, 우리는 즉시 가용성을 복원하기 위해 임시 패치를 적용. 우리는 그런 다음 루트 원인을 확인하고 영구적인 수정을 구현했습니다.
모든 서비스는 일반적으로 운영됩니다.
postmortem
#### 요약
5:44 및 5:57 AM EST 사이의 사건 경험
우리는 혼란에 대해 죄송합니다.
### 무슨 일이 있었는지 \(고수준 \)
이 사건은 원 애플리케이션의 누락 된 구성으로 인해 새로운 코드 변경을 원 애플리케이션에 배포하는 데 사용됩니다.
#### 소송 및 즉각적인 수정
문제가 발생하면 즉시 애플리케이션 가용성을 복원하는 임시 변경으로이 응용 프로그램을 패치했습니다.
나중에 오늘, 우리는 루트 원인을 확인하고 definitive 수정을 적용.
#### 상태
모든 서비스는 현재 운영 중입니다.
공식 인시던트 업데이트를 자동 번역했습니다.
app.circle.so는 아래로 입니다
시작 2026년 10월 3일 오전 8:13 UTC · 5m
Pending
investigating
우리는 현재이 문제를 조사하고 있습니다.
resolved
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
app.circle.so는 아래로 입니다
시작 2026년 9월 1일 오후 1:59 UTC · 51m
Pending
investigating
우리는 현재이 문제를 조사하고 있습니다.
resolved
오늘, 우리는 9:59–10:50 AM에서 간단한 서비스 붕괴 경험 예정된 보안 업데이트 중 ET. 서비스는 완전히 복원되었습니다, 그리고 우리는 다시 일어나서 이것을 방지하기 위하여 장소에 있는 safeguard를 둘 것입니다. 우리는 어떤 불편든지를 위해 apologize.
The issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
The issue has been fully resolved and all systems are operating normally. A detailed post-mortem report will be published here shortly. Thank you for your patience and cooperation.
postmortem
## Delays in Asynchronous Actions and Workflows
**Issue Summary** On May 28, 2026, we experienced an incident that caused delays in asynchronous actions and automated workflows.
**Timeline \(UTC\)**
* **11:29** – The issue began, causing delays in newly scheduled automated workflows.
* **15:51** – Our engineering team identified the root cause of the scheduling interruption.
* **16:42** – A fix was deployed, restoring normal operations to the background processing framework.
* **18:45** – The resulting backlog of delayed tasks was completely cleared and normal service was confirmed.
**Root Cause** A routine system update included a software dependency upgrade that unexpectedly conflicted with our background processing framework. This conflict prevented scheduled background jobs from moving into the active processing queue. As a result, automated workflows and other asynchronous actions were delayed, though no underlying data was lost or corrupted during this time.
**Resolution** Upon investigating the anomaly in the scheduling queue, our engineering team determined that the recent dependency upgrade was responsible. We immediately reverted the update, which restored the flow of scheduled tasks. To resolve the issue as swiftly as possible, we temporarily scaled up our infrastructure's processing capacity to rapidly clear the backlog of delayed actions.
**Preventative Measures** To prevent this type of issue from occurring in the future, we are planning on implementing the following improvements:
* **Enhanced Alerting:** We are deploying strict, automated alerts specifically designed to detect anomalies in scheduled task queues, drastically reducing our time to detection.
* **Upgraded Telemetry:** We are adding granular, time-series visualizations to our monitoring systems to better track the exact states of background jobs \(scheduled, enqueued, and processed\) in real time.
We sincerely apologize for any disruption this may have caused to your operations. The issue was fully mitigated, and all backlogged tasks have been successfully processed.
app.circle.so is down
시작 2026년 5월 22일 오후 1:26 UTC · 2m
Pending
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
app.circle.so is down
시작 2026년 5월 20일 오후 4:12 UTC · 1m
Pending
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
app.circle.so is down
시작 2026년 5월 9일 오전 3:12 UTC · 1m
Pending
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
app.circle.so is down
시작 2026년 4월 30일 오후 6:00 UTC · 1h 43m
Pending
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
postmortem
Some users experienced an issue where app.circle.so was unavailable. This was caused by the Redis cluster reaching 100% CPU due to a large volume of workflow jobs being re-enqueued. We identified the root cause, scaled down the background deployment pods to relieve the load, and restored service within approximately 3 minutes. We are continuing to investigate and address the underlying issue.
Search functionality was degraded starting at approximately 6:52 PM EDT on April 14. The issue was caused by Elasticsearch cluster degradation. An incident report was filed internally. This issue should have had a status page entry since customers reported broken search.
Customers checking [status.circle.so](http://status.circle.so) saw 'All Systems Operational' during this period.
postmortem
Search functionality was degraded starting at approximately 6:52 PM EDT on April 14. The issue was caused by Elasticsearch cluster degradation. An incident report was filed internally. This issue should have had a status page entry since customers reported broken search.
Customers checking [status.circle.so](http://status.circle.so/) saw 'All Systems Operational' during this period.
app.circle.so is down
시작 2026년 4월 14일 오전 4:17 UTC · 4m
Issues경미한 인시던트
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
postmortem
Communities experienced approximately 19 minutes of downtime starting at 12:17 AM EDT. The database crashed due to an out-of-memory error at the infrastructure level, a known AWS RDS bug. Our team raised a second escalation to AWS \(case 177616832700336\), and both cases have been escalated to AWS's highest priority tier. We are actively working with AWS to resolve the underlying infrastructure issue and have additional safeguards in place.
