SAP

Troubleshooting Gateway Timeout When Triggering SAP BTP APIM Endpoint

Sergei Ignatov

Feb 6, 2024 — 3 min read

SAP BTP requires no introduction, being well-established among SAP developers and consultants. In this brief discussion, we'll address an issue encountered within SAP APIM (API Management), a component of the SAP BTP Integration Suite, which may result in intermittent errors such as 'broken pipe error' or 'gateway timeout.

Scenario description

You're utilizing APIM on your BTP instance to expose the Integration Flow Endpoint as an API and test the flow. This API initiates an HTTP request to a third-party system, awaits a response for processing, and then forwards the response message to the client.

See. Expose Integration Flow Endpoint as API and Test the Flow

Issue description

Upon triggering the API's endpoint via, for example, the Postman client, you may encounter a 'gateway timeout' error if the HTTP call to the external system exceeds or equals 55 seconds.

Demonstration

To illustrate, let's use an API that triggers a simple iflow, including a Groovy script step simulating an HTTP call lasting for 55 seconds.

See. Developing Script and Script Collection

Upon triggering the exposed API endpoint, a 'Gateway timeout' error occurs after 55 seconds.

Adjusting the timeout value to 54 seconds results in a successful API trigger with a 200 response code, indicating successful processing and response retrieval.

Root cause

The default timeout value in SAP APIM is set to 55 seconds, intended to accommodate request, response, and processing times. Exceeding this threshold may result in timeout errors, including the 'broken pipe error'.

See SAP Note 3336835 - Custom timeout at API Management level

Basically it's not recommended to have timeout value of more than 55sec for a proxy. 55 seconds has been set as the default IO timeout so that if there is no data to read or if the socket is not ready to write data within 55 seconds, the transaction is treated as a timeout.

PDF version of SAP Note 3336835 - Custom timeout at API Management level

💡

As of 24 Apr, 2024 the above SAP Note has been removed by the vendor.

To address this issue, you may consider options such as:

Requesting an increase in the timeout limit to 5 minutes through an OSS message to SAP
Optimizing HTTP requests to reduce processing time and enhance efficiency.
Redesigning your flow implementing the asynchronous call as per description from the SAP Note SAP Note 3336835 - Custom timeout at API Management level

Resolving Issues with PGP Decryption in SAP BTP iFlow

Hey there! I want to address an issue that may arise in projects involving encryption/decryption within the SAP BTP iFlow and its embedded PGP engine. Scenario description Imagine you've installed the latest version of the gpg4win application (version 4.3.1) to generate public and secret keys

Creating an API for iFlow: A Step-by-Step Guide

This guide aims to outline the steps required to create an API for iFlow and subsequently run the iFlow through the API. Step # 1. Develop an iFlow Begin by creating a simple iFlow. Deploy any changes made. Step # 2. Setting Up API Providers Navigate to the API section on the

Logging the iFlow's payload

This note contains an example of a Groovy script that may help the developer trace the payload within the iFlow, especially if it changes during its lifecycle. It is worth noting that the beauty of the script below is that it adds an attachment to the processed message that can

Overwriting standard BTP iFlow header parameters

This brief note aims to highlight the possibility of overwriting standard iFlow header parameters, offering developers flexibility in addressing various requirements. Specifically, this discussion centers around the header parameters SAP_Sender and SAP_Receiver. See Headers and Exchange Properties Provided by the Integration Framework SAP allows developers to overwrite the