Hello everybody,   Here also a lot of errors on the API gateway especially the last two days and also this afternoon at 13:14. API is still not working well, but status says it's OK.     Message              Status   ResponseStream             ResponseWebHeaderCollection ResponseUri      ResponseStatusCode                ResponseStatusDescription        DC_DateTimeStamp   The remote server returned an error: (502) Bad Gateway.            ProtocolError {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5102","ExceptionMessageID":"5102_f7c5e633-60e6-4d13-bc93-b8b69047658d","ExceptionDetails":""}              Transfer-Encoding: chunked Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: d6fd7fce-e103-4ce1-809a-737545c12fdd Request-Context: appId=cid-v1:22f66f91-b042-4660-9803-ec9d7e371cb3 Content-Type: application/json Date: Wed, 25 Oct 2023 13:14:04 GMT ETag: "6538b067-8f2"                   https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202002&pageSize=1000&pageNumber=12     502        Bad Gateway     2023-10-25 15:14:04.961 The remote server returned an error: (500) Internal Server Error.              ProtocolError {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_4f743394-9353-418d-b173-b3b105f24d6a","ExceptionDetails":""} Pragma: no-cache Transfer-Encoding: chunked Strict-Transport-Security: max-age=31536000; includeSubDomains,max-age=31536000; includeSubDomains ipp-request-id: a00d3fb6-8923-48b9-b57c-5f032833d00c X-Content-Type-Options: application/json X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin Access-Control-Expose-Headers: Request-Context Content-Security-Policy: frame-ancestors *.visma.net erp096701000039 localhost Feature-Policy: geolocation 'none'; vr 'none'; payment 'none'; midi 'none'; microphone 'none'; fullscreen 'none'; encrypted-media 'none'; camera 'none'; autoplay 'none'; X-XSS-Protection: 1;mode=block Request-Context: appId=cid-v1:22f66f91-b042-4660-9803-ec9d7e371cb3 Cache-Control: no-cache,no-cache Content-Type: application/json Date: Wed, 25 Oct 2023 13:12:28 GMT Expires: -1                   https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202002&pageSize=1000&pageNumber=9        500        Internal Server Error       2023-10-25 15:12:28.956   We also had 13 errors the last three months, but since the last two days we get errors every time.   Any indication when this will be resolved? Overview:   Message 24-10-2023 22:55 System.Net.WebException: The remote server returned an error: (500) Internal Server Error. 23-10-2023 22:37 System.Net.WebException: The remote server returned an error: (500) Internal Server Error. 6-10-2023 22:44 System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host 4-10-2023 00:30 System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.     Kind Regards, Frank Schimmel Hogeschool Leiden ... View more

Hi Magnus,   Since last Friday we did not have any trouble getting the data. Has anything changed on your side?   Kind regards, Frank ... View more

Hi Magnus, We do not have a retry mechanism because it used to work fine. It happens randomly around once in '800' calls. We do about 2000 calls to retrieve all the records.   Thanks, Frank ... View more

Problem is still occurring.  The connection is not only lost with the journal transactions, but it happens randomly when many pages are retrieved. For example, it also happend with retrieving costumerinvoice that got a 0 byte response and stopped the connection. Anyone of Visma looking into this problem?   Kind regards, Frank ... View more

Hi Magnus,   Our import went well for the past two weeks, but last monday (4th of october) we had another 'Timeout' and the import stopped at 01:26:08. Did you have any other troubles that night? Can you see if there is any cause. Is there too much traffic on the server at this time?     Timestamp Method URL Response code Service response code Request size Response size Response time Service response time Chace IP address Service region 10/04/2021, 01:25:58 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202005&pageSize=1000&pageNumber=4 200 200 638 B 1.29 MB 2.01 s 1.99 s None 195.169.84.220 West Europe 10/04/2021, 01:26:00 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202005&pageSize=1000&pageNumber=5 200 200 638 B 1.29 MB 1.99 s 1.98 s None 195.169.84.220 West Europe 10/04/2021, 01:26:02 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202005&pageSize=1000&pageNumber=6 200 200 638 B 1.29 MB 3.41 s 3.39 s None 195.169.84.220 West Europe 10/04/2021, 01:26:06 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202005&pageSize=1000&pageNumber=7 200 200 638 B 1.29 MB 2.31 s 2.3 s None 195.169.84.220 West Europe 10/04/2021, 01:26:08 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202005&pageSize=1000&pageNumber=8 0   0 B 0 B 1.67 mins 1.67 mins None 195.169.84.220 West Europe   Kind regards,   Frank Schimmel ... View more

Hi Magnus,   When we do the same import batch starting at 6:30 we have had no issues or timeouts. When an import starts and we recieve an error, the import stops. We do not do retry's of API calls after one has failed.   Kind regards, Frank Schimmel Our  Company ID=838682\   Kind regards, Frank ... View more

Hello Magnus,  Last night we have had another 'Gateway timeout' 504 error at 1:52:50 (last entry in this table): 09/17/2021, 01:52:29 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202107&pageSize=1000&pageNumber=19 200 200 639 B 990.18 kB 3.2 s 3.19 s None 195.169.84.220 West Europe 8b24b6ce-1351-4695-b410-5fe327e5ba51 09/17/2021, 01:52:32 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202107&pageSize=1000&pageNumber=20 200 200 639 B 999.97 kB 3.32 s 3.31 s None 195.169.84.220 West Europe 287027eb-ffda-41a0-b8b2-2fe1f288be7d 09/17/2021, 01:52:36 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202107&pageSize=1000&pageNumber=21 200 200 639 B 986.91 kB 3.29 s 3.28 s None 195.169.84.220 West Europe aa5d823d-308f-43c4-8219-042edd90477b 09/17/2021, 01:52:39 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202107&pageSize=1000&pageNumber=22 200 200 639 B 973.74 kB 3.44 s 3.42 s None 195.169.84.220 West Europe 681ca658-ba30-4dfe-b1ce-73dcece1f290 09/17/2021, 01:52:42 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202107&pageSize=1000&pageNumber=23 200 200 639 B 983.05 kB 3.79 s 3.78 s None 195.169.84.220 West Europe 517b273f-1f79-4d40-ab13-8dac8bde34cc 09/17/2021, 01:52:46 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202107&pageSize=1000&pageNumber=24 200 200 639 B 998.55 kB 4.02 s 4.01 s None 195.169.84.220 West Europe da7a4bd1-7c6a-4c95-8360-821e8d48a24f 09/17/2021, 01:52:50 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v2/journaltransaction?periodId=202107&pageSize=1000&pageNumber=25 504 504 639 B 401 B ... View more

Hello Magnus,   Last night we have set our import time of Visma that started at 6:30 back to 1:20 midnight (CET), and now we got a timeout again. It looks like the extra API server performance is not enough at this time of the night.   We got a 504 response at 01:56:44 and the import stopped.  This is our API log that started at 1:20     09/14/2021, 01:55:45 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=2 200 200 619 B 3.26 MB 8.92 s 8.89 s 195.169.84.220 09/14/2021, 01:55:54 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=3 200 200 619 B 3.26 MB 8.61 s 8.59 s 195.169.84.220 09/14/2021, 01:56:03 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=4 200 200 619 B 3.26 MB 8.74 s 8.72 s 195.169.84.220 09/14/2021, 01:56:12 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=5 200 200 619 B 3.26 MB 12.61 s 12.58 s 195.169.84.220 09/14/2021, 01:56:24 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=6 200 200 619 B 3.69 MB 12.06 s 12.04 s 195.169.84.220 09/14/2021, 01:56:37 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=7 200 200 619 B 2.47 MB 7.46 s 7.44 s 195.169.84.220 09/14/2021, 01:56:44 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=8 504 504 619 B 401 B 10.17 s 10.17 s 195.169.84.220       We restarted the import at 6:30. This import went fine and continued till the end.     /2021, 07:06:02 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=5 200 200 619 B 3.26 MB 14.21 s 14.19 s None 195.169.84.220 09/14/2021, 07:06:17 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=6 200 200 619 B 3.69 MB 9.37 s 9.34 s None 195.169.84.220 09/14/2021, 07:06:26 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=7 200 200 619 B 2.47 MB 7.54 s 7.52 s None 195.169.84.220 09/14/2021, 07:06:34 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/customerinvoice?pageSize=1000&pageNumber=8 200 200 619 B 1.03 kB 1.26 s 1.26 s None 195.169.84.220 09/14/2021, 07:06:35 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/project?pageSize=1000&pageNumber=1 200 200 611 B 332.56 kB 9.22 s 9.22 s None 195.169.84.220 09/14/2021, 07:06:44 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/project?pageSize=1000&pageNumber=2 200 200 611 B 1.03 kB 602.04 ms 601.48 ms None 195.169.84.220 09/14/2021, 07:06:45 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/projectbudget?pageSize=1000&pageNumber=1 200 200 617 B 464.43 kB 1.05 s 1.04 s None 195.169.84.220 09/14/2021, 07:06:46 AM GET https://api.hsleiden.nl/provider/visma/visma_stichting_hsl/v1/projectbudget?pageSize=1000&pageNumber=2 200 200 617 B 1.03 kB 437.78 ms 437.28 ms None 195.169.84.220     Can you see any performance troubles at around 1:56 last night?   Kind regards, Frank Schimmel                   ... View more

Hi Magnus,   Thanks you for the answer and good that you are monitoring.   Kind regards, Frank ... View more

Hello people of Visma,   We have had the same problems with the Visma API. We import all the info of Visma into our Information Framework. Problems started on 12th of august with (403) errors (Forbidden) and then from 20/8 we have had operation time outs. Now it all seems fine again. But the question is, did something change on the 12th of august that has caused all this problems and is Visma monitoring time outs to prevent this problems in the future? Log overview:   ## Succeeded VismaApi ExtractJSON.dtsx 26-8-2021 09:15:03 26-8-2021 10:11:54 3411,403 1 Hand       ## Failed VismaApi ExtractJSON.dtsx 25-8-2021 23:20:00 25-8-2021 23:23:52 231,368 1 Sched The operation has timed out JournalTransaction 202001   ## Succeeded VismaApi ExtractJSON.dtsx 24-8-2021 23:20:01 25-8-2021 00:45:27 5126,278 1 Sched       ## Succeeded VismaApi ExtractJSON.dtsx 24-8-2021 11:47:36 24-8-2021 12:39:08 3091,611 1 Hand       ## Succeeded VismaApi ExtractJSON.dtsx 23-8-2021 11:30:01 23-8-2021 12:39:36 4175,445 1 Sched       ## Succeeded VismaApi ExtractJSON.dtsx 23-8-2021 09:05:19 23-8-2021 09:57:43 3144,755 1 Hand       ## Failed VismaApi ExtractJSON.dtsx 23-8-2021 01:20:01 23-8-2021 01:32:54 773,356 1 Sched The remote server returned an error: (502) Bad Gateway. JournalTransaction 202006   ## Succeeded VismaApi ExtractJSON.dtsx 20-8-2021 10:28:41 20-8-2021 11:28:12 3571,425 1 Hand       ## Failed VismaApi ExtractJSON.dtsx 20-8-2021 01:20:01 20-8-2021 01:48:09 1687,998 1 Sched The operation has timed out JournalTransaction 202011   ## Succeeded VismaApi ExtractJSON.dtsx 19-8-2021 10:29:10 19-8-2021 11:40:11 4261,746 1 Hand       ## Failed VismaApi ExtractJSON.dtsx 19-8-2021 01:20:01 19-8-2021 01:20:05 4,125 1 Sched The remote server returned an error: (403) Forbidden. JournalTransaction 202000   ## Failed VismaApi ExtractJSON.dtsx 18-8-2021 01:20:01 18-8-2021 01:20:04 3,626 1 Sched The remote server returned an error: (403) Forbidden. JournalTransaction 202000   ## Failed VismaApi ExtractJSON.dtsx 17-8-2021 01:20:01 17-8-2021 01:20:05 4 1 Sched The remote server returned an error: (403) Forbidden. JournalTransaction 202000   ## Failed VismaApi ExtractJSON.dtsx 16-8-2021 01:20:00 16-8-2021 01:20:04 3,906 1 Sched The remote server returned an error: (403) Forbidden. JournalTransaction 202000   ## Failed VismaApi ExtractJSON.dtsx 13-8-2021 01:20:01 13-8-2021 02:01:02 2461,044 1 Sched The remote server returned an error: (403) Forbidden. Supplier   ## Failed VismaApi ExtractJSON.dtsx 12-8-2021 01:20:01 12-8-2021 02:03:54 2633,279 1 Sched The remote server returned an error: (500) Internal Server Error. Ledger   ## Succeeded VismaApi ExtractJSON.dtsx 11-8-2021 01:20:01 11-8-2021 02:09:13 2951,615 1 Sched       Kind regards, Frank Schimmel   ... View more