I can basically confirm it is *some*
I can basically confirm it is some issue with browser rendering + queues. The only thing I changed was moving the browser rendering logic to a DO and calling that instead of it just being a function in my consumer. The rest of the logic is the same, and I have not had the issue since making that change
4 Replies
thanks for highlighting this! And also thank you @Poyo! I was able to replicate this issue - it's probably a bug on our side
Hi Pranshu, Is the current best way to run a long browser renderer via a DO Alarm?
Or are we be able to run the browser renderer from the que?
I can confirm there is an issue right now with browser rendering inside a queue consumer. we're working on it, but too soon to share a timeline. if you're building something right now, it might be best to move the browser rendering logic to a DO
Thanks for the reply and happy to help! 🫡