Running on AWS Lambda, the PromisePool resolves after the first batch, does not run till the end

[ccovarrubias]

Version

nodejs14.x

Platform

AWS lambda

Subsystem

Amazon AMI

What steps will reproduce the bug?

No response

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

When I run this code:

await PromisePool.withConcurrency(concurrency)
      .for(this.crawledData)
      .handleError(async (error) => {
        console.log("handled error occurred:",error)
        return
      })
      .process(async (link) => {
        const page = await this.browser.newPage();
        console.log("getting more related models.. ", link.url);
        await this.browser.goToUrl(`${link.url}`, page);
        console.log("loaded!")
        const a = this.crawledData.length;

        const relatedHrefs = (await this.browser.gethrefs(`main a[href*="${link.category}`),page)
        if(Array.isArray(relatedHrefs)){
          const related = relatedHrefs
          .filter((x) => x.replace(homeUrl, "").split("/").length == 2)
          .map((d) => carUrlJson(d))
          .filter((x) => !this.cars.includes(x.url_model))
          this.crawledData = this.crawledData.concat(related);
        }
        this.cars = uniquesInArray(this.crawledData.map((x) => x.url_model));
        const b = this.crawledData.length;
        console.log(`${b - a} found`);
        await this.navigateCar(link,page);
        await this.browser.closePage(page);
      });

inside an AWS lambda handler, I expect the first await to resolve until the end of my crawledData array.

What do you see instead?

e.g., If I set concurrency = 5, The lambda exits after the first 5 iterated elements; it seems that the external await receives the resolve signal from the PromisePool and continues with the code execution, that (in my case) results in the end of the process and kills the execution.

Additional information

Any help or suggestion will be appreciated!