Unexpected Long Worker Execution Times When Using Browser Rendering in Cron Trigger

Developers Workers
1

For Workers & Pages, what is the name of the domain?

What is the issue or error you’re encountering

Unusually long worker execution times when using Browser Rendering in Cron Triggers, sometimes resulting in timeouts.

What steps have you taken to resolve the issue?

I’ve implemented browser session reuse as described in the documentation: Reuse sessions · Browser Rendering docs
This prevented timeouts, but execution times remain abnormally long compared to using the same browser rendering code with fetch handlers.
I’ve also added logging to confirm that the browser operations themselves complete successfully, but the worker continues running for an extended period afterward.

What are the steps to reproduce the issue?

export default {
  async scheduled(event, env, ctx) {
    await doSomeBrowserTask();
  },
};

When executed via Cron Trigger, this code has much longer execution times than when the same browser rendering tasks are called through a fetch handler.