Workflow or API calls:
Reminder: If this is referring to a client domain or EHR activity—not the public sandbox—do not include API request data or live patient data.
Background Information:
Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:
Are you an OPN Member? Yes (Tangible Solutions)
Have you signed up to be in the Healthcare Developer Track? Yes
Are you a registered Code Program member? Yes / No
Does your App have a presence on the Oracle Healthcare App Marketplace? Yes / No
Are you developing on behalf of an Oracle Health client?
If so, which client:
Application's Client ID and App ID, if relevant:
Application ID
847065ab-9b41-4b54-9084-d1a11c79c5e0
Client ID
d68da736-2824-4ebb-a452-701af4ccce39
Expected Result:
Expected a response containing a JSON string with an embedded base64 encoded PDF document
Actual Result:
When requesting the PDF version of the Binary we received an ErrorException {"Request failed with status code GatewayTimeout"} with the Content {"message":"Gateway Timeout","code":504} after about 60 seconds delay.
When requesting the XML version of the same document it gets returned successfully almost instantaneously. This seems to suggest something is failing within the tenant sandbox when generating the PDF from the XML. Other PDF documents from this same tenant and patient return correctly.
Our research suggests the following:
The error message "Gateway Time-out" with a status code of 504 indicates that the server, acting as a gateway or proxy, did not receive a timely response from the upstream server. Essentially, the request to the upstream server timed out.
This could be due to several reasons:
- Server Overload: The upstream server might be overloaded or experiencing high traffic, causing delays in processing the request.
- Network Issues: There could be network latency or connectivity issues between the gateway and the upstream server.
- Resource Intensive Requests: The request might be too resource-intensive, taking longer than expected to process.
To resolve this, you might want to:
- Check the upstream server's status: Ensure it's not overloaded or experiencing issues.
- Optimize the request: Simplify or break down the request into smaller parts if possible.
- Increase timeout settings: Adjust the timeout settings on the gateway server if feasible.
The issue happens every time this specific document is requested even at different times of day which suggests it is unlikely to be a server overload or a network issue.
Can you please advise on the solution either on our client side or the tenant side? Is it possible this will only ever happen in the sandbox or is it also possible in the production environment?
X-Request-Id / Cerner-Correlation-Id / opc-request-id:
[5] = {opc-request-id=/B8D9F0160921D44F1FB7749F818E6482/2DCC3EDFE8CF400C40EB7E479CA55AC6}
Date/time of the example:
[2] = {Date=Thu, 21 Nov 2024 02:45:09 GMT}
Thanks,
Chris