Code bug
StandardError
[Medplum::Client] GET Practitioner/<secret> failed with HTTP 410: {"resourceType":"OperationOutcome","id":"gone","issue":[{"severity":"error","code":"deleted","details":{"text":"Gone"}}],"extension":[{"url":"https://medplum.com/fhir/StructureDefinition/tracing","extension":[{"url":"requestId","valueId":"<secret>"},{"url":"traceId","valueId":"<secret>"}]}]}
In one line
A staging rake task pages through all Medplum Patients with _offset and hits Medplum's 10,000 offset cap. The 400 is then reported to Bugsnag as a warning by Medplum::Client.
Checked against the code
What happened
- A rake task loops over `Patient?_count=1000&_offset=N` and reaches offset 11000.
- Medplum rejects any offset above 10000 with HTTP 400, so the loop cannot go past about 10k patients.
- `Medplum::Client#report_failure` sends every non-401, non-412 failure to Bugsnag, so each run of the task raises this alert.
- There are 439 events from 18 users over 10 days, all on staging. That fits a task run repeatedly and failing at the same offset, not a one-off deploy problem.
What to do next
- Check Find the rake task named in the Bugsnag trace (the file name is redacted) on the deployed release 0.2.0:20261111104530. Compare it with releases/master, which I could not match to any task that pages Patient with _count=1000 and a growing _offset. Decide whether to delete it or to page with a keyset (`_sort=_lastUpdated` plus `_lastUpdated=gt<last>`) instead of _offset.
- Check Check the Bugsnag event's `process_type` and the staging cron or scheduler for what starts this task, and how often it runs.
Queries are shown, never run. Check them before using them on production.
Ask a follow-up
Continues the same session, so it still remembers the error and the code it read.
Analysed 1 h ago · claude-sonnet-5-5 · $0.14