Is there a limit to the wsproxy limit?

Is there a limit to the wsproxy limit?

The Retrieve method is designed to return multiple items (but can be a single item if filtered that way) with a maximum of 2500 records. This maximum is true for all SOAP API retrieves and is not a WSProxy limit. To get around this, you will need to utilize the getNextBatch function.

What does wsproxy mean in JavaScript in SFMC?

WSProxy in SFMC is a script object that is native to the platform and allows for communication with most available SOAP objects through platform authentication. It utilizes SSJS and JSON syntax to make these calls via the platform inside of Script Activities or CloudPages.

Why do we need wsproxy in JavaScript?

WSProxy reduces overhead and increases the speed of your API calls, while maintaining the same ‘internal’ security level. The security is maintained as it is being authenticated via the platform (no need to include a user/pass or authentication token in the calls).


Why is there a limit on number of batches?

Please remove a batch before you add another one ”. The main reason why this number of batches limit is in place is that having more than 100 batches causes performance problems and could cause outages for other customers in the multi-tenant system. Additional reading on resourcing for mailbox moves can be found here .

How to not run into 100 migration batches?

To do this, first ensure that you have fewer than 100 batches created at the moment: Then, proceed with PowerShell commands to get the users from the larger batch Batch_1 into the new smaller batch CompletionABC. Then complete this smaller batch and optionally, remove the completed migration batch:

What is the benefit of Reducing batch size?

Small batches go through the system more quickly and with less variability, which fosters faster learning. The reason for the faster speed is obvious. The reduced variability results from the smaller number of items in the batch.