This error message is displayed, for example, when signing a payment order. The cause is that a preconfigured size limit has been exceeded, which is reached at approx. 250 payment records in a payment order.

As a user, you can avoid this error by limiting payment orders to a maximum of 250 payment records.

If this is not possible, you can increase the maximum URL length in the configuration file production.conf. On an installation server, the change must be carried out by a system administrator. For local installation, you need local administrator rights.

1. Open the subdirectory conf in the installation directory of BL Banking Web, e.g. under Windows C:\Program Files\blbankingweb\conf\.
2. Open the file production.conf with a text editor.
3. Insert the following line at the end of the file: akka.http.parsing.max-uri-length = 8k

8K (= 8000) is an example value with which approx. 1000 payment records are possible in one payment. Enter the value that you estimate to be sufficient and check whether the error message no longer occurs in the same use case.

FAQ 243

This behavior can occur after an update. The cause is that the HAA order (download retrievable services/BTF) is not evaluated. In this case, it is useful to update the bank details.

1. Open Settings – Banks.
2. Select the relevant bank in the first column.
3. Click on the button Update bank access.

In the dialog Retrieve file from the bank, the retrieval method From current provision is again limited to the specified order types.

FAQ 260