We're encountering a 404 Not Found error when attempting to retrieve binary references within the DocumentReference resource. This issue doesn't seem to be facility-specific, as we've observed it across 10+ facilities.
Here are a couple of recent examples from September 19th 13:46 EST:
- X-Request-Id: /48C7B9EA2880A1CDB33D9976EE2674F2+q2C2_EwXz
- X-Request-Id: /A4789576233CB1F8A173B3D6452B7BE2+ocIx_pNE5
- X-Request-Id: /24C5D97270E16696B269B026B7CA48F4+V4YP_BZJn
Why are these binaries being referenced in the DocumentReference resource but not reachable? According to your documentation, a 404 error indicates the resource does not exist. Can you investigate what is occurring?