Memory Threshold Issue

The only sustainable solution is to refactor your design. Think of batching, looping etc.

Thanks Stefan for your prompt response.

But we are using this data for reporting purpose. The aggregation functions are applied on the whole data so how can we apply batching logic in it.

Then you need to optimize your query. Do your really need all data returned? Is this about reporting into Excel or charts?

One possibility might be Execute Stored Procedure.  That can also be called upon to run a database FUNCTION, which can return simply the results of your aggregation.  I assume you just want things like COUNT, AVE, MIN, MAX.  You can have the DB run all the aggregation calculations and have it return only the few integers you need, if what you need is a few integers.  That way, you don't have to bring the whole dataset to bear for Appian to perform aggregation, but let the DB do it.

Considering that you seem to be fetching "listofIDtodelete" - how many columns are you returning in your query?

We are fetching only a single column (ID) of the database table but there are over 2 Lakh rows.

Then I defer to 's original suggestion of employing Batching somehow within your process.

Could you do the "heavy lifting" in the database itself? That is, use the database aggregation functions to generate a view (virtual or materialised) and then point Appian at the result table in order to present the data.

I think we need to take a step back - what is your use case? There might be a completely different query you could run depending on what you're trying to do. How are you using this data? What is the goal?

Hi Peter,

Using expression rule, We are fetching all the IDs from the database table and passing it to script task in the process model as the 'IDs to be deleted'.

While we are executing this process model, it is failing on this script task and throwing the above error.