Past incidents affecting our services
-
Resolved: Marked as fixed; we’ll apply a proper long-term fix.
-
Resolved: Incorrect workflow status fixed to real status
-
Resolved: Declined: Done
-
Resolved: Fixed the credit reservation locking that was causing workflows to pile up in retries, which in turn was overloading the API, the database connections, and the Temporal workers. Follow-ups tracked: redesign the credit reservation flow to scale per client and cap the size of deep-search results so workers don't run out of memory under load.
-
Resolved: Enrich w phone: Marked 1 missing row as completed Enrich w email: marked 1 row as cancelled as process did not complete
-
Resolved: Reset orphan stuck workflows in temporal. This may show the user incorrect data on the workflow's report results
-
Resolved: manually set the activity to cancelled to the user.
-
Resolved: Service has recovered and the app is working again; missing DB field/migration issue has been addressed.
-
Resolved: The fix has been deployed and the web app is loading normally again. If you still see issues, please refresh and try again.
-
Resolved: Resolved: Enrich workers stabilized after continuing the affected Temporal workflow as new; enrichment processing recovering.
-
Resolved: Fix deployed
-
Resolved: fixed
-
Resolved: Google SSO login is back to normal. If you still see issues, retry login or contact support.
-
Resolved: Resolved: performance has recovered after scaling instances and reducing cached workflows; task backlog is back to normal.
-
Resolved: Resolved: API service is stable again; no further instance deaths observed. We’ll continue monitoring.
-
Resolved: Fix deployed and tested; issue no longer reproducible.
-
Resolved: We added a fix for the conflicting variable name
-
Resolved: API performance has returned to normal and instance health looks stable.