I should start this off by saying that I know list execution jobs are in preview, and not yet fully supported. This is more feedback/suggestion than anything else.
List execution jobs created through the List Execution Job (Create) endpoint have a habit of failing and returning System.OutOfMemoryException exceptions after running for an hour or so. This mostly happens when running larger advanced lists (70k to 80k rows), but it's not exclusive to large lists.
In the rare case when they do succeed, the largest list is about 10-15MB at the most; so they're not super massive. The same advanced lists tend to succeed more frequently when requested page-by-page through the List Single endpoint.
The ability to use list execution jobs to run larger lists would be extremely helpful, as currently we're having to run 90 or so requests to paginate through some lists, and it's cumbersome. The list execution jobs don't need to be lightning-fast, as long as they're reliable.
Anybody else experiencing similar System.OutOfMemoryException exceptions with list execution jobs?
