Discussions
202 Response Without processId
24 days ago by Sievers Group
During our recent stress tests, we observed an issue.
When sending a large number of requests (over 10,000 in a short time frame), we noticed that around the 4,300th request, the responses returned with HTTP status 202, but without a corresponding processId in the response body.
Please note that we have already implemented a limit of 500 requests on our side, but the issue still persists under high load.
Could this behavior be related to an internal technical limitation on your side? We would appreciate it if you could investigate this and provide further guidance.
Best regards