High load, slow response when changing password for user with a lot of documents

Technical Support
2

Confirming some important findings:

  1. when you experience the Warning! This user would replicate... error, the password change does not take effect.
  2. curl takes just a few seconds and does indeed work using the user API. Be sure to replace MRJONES-NEW-PASSWORD , MEDIC-PASSWORD and CHT-URL with real values:
    curl --header "Content-Type: application/json"  \
 --request POST  \
 --data '{"password":"MRJONES-NEW-PASSWORD"}' \
 https://medic:MEDIC-PASSWORD@CHT-URL/api/v1/users/mrjones

I believe maybe this error was in API logs at the time of the error? It may be unrelated:

2025-10-14T21:35:13.703 RES: 4194e2cce496 75.83.68.217 - POST /medic/_bulk_get?revs=true&attachments=true HTTP/1.0 200 - 14253.895 ms
2025-10-14T21:35:14.154 ERROR: Error on Log Replication Limit Error: Error when persisting log: Log Information missing.
    at persistLog (/service/api/src/services/replication-limit-log.js:14:19)
    at Object.logReplicationLimit [as put] (/service/api/src/services/replication-limit-log.js:87:10)
    at Object.getContext (/service/api/src/services/replication.js:19:29)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async getAllowedDocsCounts (/service/api/src/controllers/users.js:100:47) {
  [stack]: [Getter/Setter],
  [message]: 'Error when persisting log: Log Information missing.'
} 
2025-10-14T21:35:14.155 RES: e11d8895074c 24.253.112.58 - GET /api/v1/users-info?contact_id=f32ec621-b457-49a9-954a-622067ef0154&facility_id=71e75e97-36a2-47c5-950b-38cb55f0d154&role=munic_level HTTP/1.0 200 66 1050865.412 ms

All in all, I think this is a bug and I’ll file a ticket later today or tomorrrow - but I wasn’t sure if it was a bug because I hadn’t seen the error message and I hadn’t tested if the password change took effect!