Not enough quota is available to process this command.

The "Not enough quota" error message typically refers to the fact that some of the local machine resources (memory, handles etc.) are running out. Using VAF background operations for the syncing might be an option but I'm not familiar with how these differ in resource handling from workflow scripts. Craig may be able to expand on that.

Thank you Joonas, we try your tip.
I'm thinking about synchronization based on automatic field in object type = start sync automatically every time it changes. Is this technique also applicable to initial synchronization for a large number of records?
O.

My personal guidance would be to move this synchronisation into a VAF background operation, as Joonas suggested. Anything else (event handler, workflow state action, etc.) will be processed synchronously and is bad architecture for synchronisation of large volumes of objects.

However, I am concerned as to the error message you're getting. If this error is being thrown by the server-side code then it indicates that there may be a resource issue on the server. If that's the case then moving the code to a VAF background operation, whilst being the correct thing to do, may not directly solve the issue (as it may still run out of resources). My suggestion would be to look at the code at the same time and see whether there are optimisations that could be made as part of the process of migrating to the background operation.

Regards,

Craig.