3807533 - SAP Build Apps — 504 Gateway Timeout After 30 Seconds When Backend Call Exceeds Default Destination Timeout

In a productive SAP Build Apps application, users get a 504 Gateway Timeout roughly 30 seconds after triggering an action (for example, clicking a Submit button that runs a "Create Record" flow).

What you typically see:

• The browser Network tab sits at "Waiting for server response" for about 30 seconds before the 504 comes back.
• The backend (BTP Integration Suite, S/4HANA, a database layer, etc.) actually processes the request successfully — logs may show a 200 or 201 — but it takes longer than 30 seconds to respond (often 1–3 minutes for complex JDBC, RFC, or OData calls).
• Adding the destination property HTML5.SocketReadTimeoutInSeconds (or other non-standard names) makes no difference — the timeout still hits at ~30 seconds.

• SAP Build Apps (Cloud)
• SAP BTP — Cloud Foundry environment
• Managed Application Router (HTML5 Applications Runtime)
• BTP Destination Service
• Any backend that takes longer than 30 seconds to respond (e.g., BTP Integration Suite with JDBC adapter, S/4HANA OData services, CAP applications)

504 Gateway Timeout, 30 seconds, HTML5.Timeout, managed approuter, destination timeout, Build Apps, Integration Suite, JDBC, long-running backend, 201 Created, timeout increase, HTML5 Applications Runtime, gateway timeout, submit, create record , KBA , CA-LCA-ACP , SAP Build Apps , Problem