504 from json api when creating duplicate party

We’re getting “upstream request timeout” on a few calls to the json api.

An example is when we try to allocate a duplicate party (which we expect to fail) via /v1/parties/allocate while the ledger api warns us in its logs about this the response back to the json api is just a 504. Are we missing something to get the ledger api to propagate back meaningful error messages to the json api?

1 Like

Hi @Turan :wave: and welcome to the Daml developer forum!

504 - Gateway Timeout, transaction failed to receive its completion within the predefined timeout