Hi Dave, there is no limit. The cause of the bottleneck needs to be identified.

WorldServer api and Tomcat logs should assist in making this determination. Please raise a support case for this providing all relevant information.

Hi Caterina,
We've actually had a case open for quite some time now (00589863). It took us forever to convince the various at teams at Bayer that the issue began after the front-end SAP app was moved to the cloud. When they did that, they also placed that SAP on the launchpad of every Bayer user.
Ryan and Thorsten Kahlich have both joined numerous calls with the various teams at Bayer and the only relief comes from reducing the number calls to WorldServer from this SAP app.I'll upload the latest statistics taken from the relevant localhost access log to the support case.

I think it may be the Custom Endpoint that needs optimization here, it was never tested in the early stage of conception with such a large user base and with the time that has passed since its creation there is every chance it could be streamlined somewhat to meet modern day WS changes.

That would be great - right now our solution has provided much-needed relief, as the number of unique users each day has dropped from a peak of just over 16,000 on 10 May to under 100 since the change. Concerns were voiced at the operational meeting yesterday re. what happens if the number of active users increases. I think we have a good buffer, but optimizing the custom endpoint would be welcomed.

That would be great - right now our solution has provided much-needed relief, as the number of unique users each day has dropped from a peak of just over 16,000 on 10 May to under 100 since the change. Concerns were voiced at the operational meeting yesterday re. what happens if the number of active users increases. I think we have a good buffer, but optimizing the custom endpoint would be welcomed.