Run task on more than the limit of records

[Shiro]

I just got a word from support that Task can only process up to 10,000 number of records only. Is there some we can still run the task if you have more than 10,000 records?

[NiceDuck]

1) Create an autonumber ID field on your table datasource.

2) On your task, create a where filter which will only process the records where id field is less than 6000 (assuming that your table has 120,000 records)

3) Duplicate this task, however, this time, set the where to filter to only include records where id field is greater than 6000.

4) Set them to run for atleast 30 mins apart. (Just a suggestion)

Hope it helps.

Quack.

[Nuke354]

To further visualize, here's a sample Task
 

[Elderberg]

 

I'm not sure the technical reasons, but is this limit associated with a lower tier plan or across all plans?  I'm curious if there is a cost to increase the limit as an add-on or if included in a higher tier plan

 

 

[sandy159]

Hello @Elderberg,

Yes,  I also faced the issue with processing only up to 10,000 number of records and this forum post helped.  I actually heard  you can buy additional records...  

I believe, it would be better to contact your Account manager straight.  They should be able to answer your questions.

Regards

[Elderberg]

thanks

[petercohen090]

Yes you can buy additional records.. i have faced this problem.

[NiceDuck]

I just discovered a new way of solving this!

What I did is I created an extra yes/no field on the table that I'm processing. 

 

 

All I have to do after that is to run the task again and again until all records are updated. The value on the TOP can be adjusted to estimate the maximum amount of record involved per run.

 

[NiceDuck]

Well, this will only works on simple Task Setup. 

 

I think the number of records being affected when a trigger activates during task run also counts on the 10k limit.