Hey Dan did stealth work out for you?

• Assuming a new session will be created each time the scheduled function starts.

async scheduled(
    event: ScheduledEvent,
    env: Env,
    ctx: ExecutionContext
  ): Promise<void> {
    const urls = [
      "https://agenty.com",
    ];
    const browser = await puppeteer.launch(env.MYBROWSER);
    await screenshot(
      browser,
      urls,
      env
    );
    await browser.close();
  }, 

async scheduled(
    event: ScheduledEvent,
    env: Env,
    ctx: ExecutionContext
  ): Promise<void> {
    const urls = [
      "https://agenty.com",
    ];
    const browser = await puppeteer.launch(env.MYBROWSER);
    await screenshot(
      browser,
      urls,
      env
    );
    await browser.close();
  }, 

• remove the

  browser.close()

  browser.close()

  line
• check that the browser is connected every fetch (

  this.browser.isConnected()

  this.browser.isConnected()

  ), and reinstantiate it if not
• do not call newPage() every fetch, instead check the browser instance and see if it has the number of pages you need already, from last time
• add an await to the setAlarm call

state.blockConcurrencyWhile()

state.blockConcurrencyWhile()

We’ve spoken to many customers deploying a Puppeteer service on their own infrastructure, on public cloud containers or functions or using managed services. The common theme that we’ve heard is that these services are costly – costly to maintain and expensive to run.

A browser instance gets killed if it does not get any command for 60 seconds, freeing one instance.