Hi Cliff,
As suggested by Youval previously, let's try to pinpoint whether the problem is with passing the file to the server or handling of it in the server, and to do that, leave the File trigger as it is, but remove the flow from it onward (I presume the the model with the File trigger is ChkForFileDuplicate).
If the memory error is repeated with this model then the problem is indeed with the actual client-server file transfer. If it is not, then the problem is with the model handling the file in the server, and your next step is to undo the flow removal, and remove instead other flows downstream, until you manage to pinpoint the problem cause.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
