What happened
What this says
As at Fri 9 Oct 2026Complaints connector paused, removing hospital data minutes before scheduled customer call. Kai Petersen restarted connector same day; data reloaded in next refresh cycle and issue resolved.
Problem: Complaints connector paused without warning, removing critical business data hours before customer call. Kai Petersen discovered the issue when preparing for the meeting.
Handling: Bethan Lister directed Kai to check connector status; Kai restarted it immediately. Data reloaded in next refresh cycle within hours.
Watch: Connector pauses should trigger alerts to prevent silent data loss during critical business moments.
Details
Updated 9 Oct 26Trail
- created · Kai Petersen 9 Sep 2026 17:53We're running a call with one of our hospital partners in a few minutes and their complaint data is missing from the brain. It was there yesterday. What's happened and can you recover it now?
- Public reply · Bethan Lister 9 Sep 2026 18:27Hi Kai, Can you check if the complaints connector is still active and running in the system? If it's paused or broken, we might need to restart it. Look under Connectors and tell me what you see for the complaints source. Thanks, Bethan
- Internal note · Bethan Lister 11 Sep 2026 10:46Customer confirms complaints connector shows as paused. Not clear why. Ewan to investigate - might be related to a system config change or API key refresh on their side.
- Public reply · Kai Petersen 11 Sep 2026 10:51I found it. The complaints connector was paused. I've restarted it. Is the data loading now?
- Public reply · Bethan Lister 11 Sep 2026 16:31Kai, Just so I've got this right: the connector is running again now? The data should start flowing back in over the next refresh cycle tonight. By tomorrow morning the complaints should be current again. If you don't see them by then, let me know and we'll dig deeper. Thanks, Bethan
- Status change · 15 Sep 2026 23:59