However, it returns > 6MB of data which causes a 503 error. I am on n8n cloud.
Do you know any solutions around the problem ?
this is the workflow I am trying to run at the moment
Hi @Ak92, I am very sorry to hear you’re having trouble here.
Seeing this isn’t binary data I don’t think there is an easy way to reduce the amount of data kept in memory here I am afraid. However, from looking at the page I think you could try calling the API used by this page directly (instead of loading the full page and then parsing it), for example like so:
As an added bonus, this saves from the cumbersome parsing work. I just tested this workflow on my own n8n.cloud instance and it seems to work fine:
I opened the console in my browser and simply checked the network tab as to what happens when playing around with the page. I then simply copied the URL of the XHR request made when changing the sorting order: