Skip to Content
Technical Articles
Author's profile photo Nils Janssen

HTML5.Timeout for CAP destinations in mta.yaml longer than default

Hello fellow SAP developers,

this will a short one but I think it might be helpful to other developers.

We had the problem, that the READ requests from our SAPUI5 application took a very long time to process in the S4/HANA backend system but were actually returning fine.

Somewhere in SAPUI5 app, the CAP middleware, the managed Approuter or the BTP we had a component that threw a Gateway Timeout issue after 30 seconds. Gateway_timeout


We searched for hours but could not find the one resource that would help us. In the end it was a combination of multiple blogs, questions and documentations that helped us.

All we had to do was to set the HTML5Timeout property to a value like 30000 in the mta.yaml like this:


Destination Timeout setting

During the deployment these destinations are created/updated in the service instance.

I hope this might help someone out there to save some time.

Don’t worry, we will work on the performance issue of the requests as well but we needed this urgently as a quick “fix”. 😉

Most of the information comes from the SAP Help library:

Thank you for reading and I am looking forward to hearing your feedback.
I will post of more those insights if I find something useful and if there is demand for it.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Volker Buzek
      Volker Buzek

      true life hack!

      Author's profile photo Nils Janssen
      Nils Janssen
      Blog Post Author

      Thank you Volker.

      Author's profile photo Michael Alekseew
      Michael Alekseew

      Thanks a lot, Nils Janssen that saved me so much time, I was already searching where I could configure timeouts in the BTP for Frontend (FE) to Backend (BE) calls.