simPRO API Forum

Posted: **Tue Apr 21, 2026 3:54 pm**

Hi All,

I've recently taken over for someone who has left the business. They've created a single AWS Glue script that gets all data from the following endpoints,

Code: Select all

    endpoints = ["contractors", "vendorOrders", "catalogs", "vendors", "invoices", "employees", "jobs",
                 "quotes", "sites", "setup/teams", "contractorInvoices", "jobWorkOrders", "jobCostCenters", "schedules"]

This includes Hierarchical data. However, the duration of this is over 7 hours and it's only going to get longer as more data is downloaded. Recently, we're getting Command failed with exit code 137. (ran out of memory and the OS killed it).

Any suggestions on getting this to work without the issues of Memory?

Would you recommend splitting each Endpoint into it's own run (Excluding the hierarchical ones)

TIA

Posted: **Wed May 06, 2026 4:08 pm**

I am also interested in any response to this

Posted: **Mon Jun 01, 2026 12:27 am**

Hello, yes this would be a substantially massive request, I would for sure be breaking up the request into a staged approach of some sort in order to make it so if a single request fails it does not fail the whole script. Also depending on the specifics I'd look into running it in parallel.

We specify an internal maximum page size to each endpoint but I'd ensure your script isn't just using the default of 30 and then requesting the following 30 as this would also be a substantial increase to the time.

Hope this helps, if you can provide anymore information on the context of the script we might be able to make some more suggestions.

Regards,

simPRO API Forum

Slow API & Eventual Memory issue

Slow API & Eventual Memory issue

Re: Slow API & Eventual Memory issue

Re: Slow API & Eventual Memory issue