Hi Stephen. Thanks for contacting Sage.

To help us diagnose the issue, can I please ask if you have any mandates in your GoCardless account outside of Sage that are not linked to a customer account in the Sage data? And if so, how many such mandates do you have?

Based on the error details a wild guess is that a very large amount of mandates is getting downloaded and that may be using the available memory space. This is just a guess based on the error, knowing how many unlinked mandates you have may narrow the issue down.

Thanks.

Hi Ali, thanks for your response. We have the same number of mandates in our GoCardless accounts as we have accounts in Sage linked to mandates, and this number has not changed for many months, and is less than 20. We were able to retrieve mandates, request payments and settlements on the 23rd March, when we tried the same actions on the same number of accounts on the 6th April, they all failed with the same error message. 

Furthermore, I have tried the same operations on a PC and directly on the copy of Sage installed on the server (27.1.562.0) and get exactly the same error message on both, so it doesn't appear to be related to the environment.

Furthermore, I have tried the same operations on a PC and directly on the copy of Sage installed on the server (27.1.562.0) and get exactly the same error message on both, so it doesn't appear to be related to the environment.

Thanks Stephen. We may need to gather some logs when you attempt the same operations again. I have sent you a private message on Sage City requesting some details so that we can contact you regarding that. Can you please check your Sage City messages? Thanks.

Sorry, only just caught up with this, will get back to you shortly with the requested info.

I didn't have a chance to do anything about this, but very strangely and spontaneously, the GoCardless routines just started working again with no error messages. So it appears to be all working again.