At 09:14, successful connector jobs drop while queue age rises. At 09:17, dashboard reads remain normal because cached records are still available. Is the source unavailable, authorization revoked, a parser rejecting new payloads, or storage failing? The first operational move should reduce further writes without turning sensitive payloads into debugging material.
The news context is OpenAI’s July 23, 2026 Health in ChatGPT announcement. OpenAI says rollout is for eligible logged-in US users 18+ on web and iOS, with supported medical-record and Apple Health connections. It says a dashboard can cover labs, medications, activity, sleep, and other health information, and states connected data and relevant conversations are not used to train foundation models or target ads. Those claims are from OpenAI’s post. This runbook is a generic operational artifact, not a description or test of OpenAI’s pipeline.
Assumed topology and safe telemetry
connector callbacks -> admission gate -> import queue -> parser -> record store
| | |
