Meera Sandhu

No. The answer is workers: process.env.CI ? 2 : undefined.

That runner is 2 vCPU shared. Four chromium contexts plus your server plus node means everything is starved, and Playwright's actionability checks are the first thing to notice - before it clicks, it waits for the element to be stable across two animation frames, visible, and not covered. On a machine where a frame takes 400ms, "stable for two frames" stops being instant and starts being a race with your own animations.

That is exactly your symptom: the button is there in the screenshot, and the click is waiting, because the thing it is waiting for is not visibility.

Expand the failed action in the trace and you will find the stability line rather than a "not found" line. Two workers on a 2-core box is usually faster in wall clock than four, because you stop paying for retries.

It is not only the disabling either. Scheduled runs can be delayed or dropped under load, so "runs most nights, sometimes 40 minutes late" is the normal state of that scheduler. Fine for a cleanup chore, not fine for something a customer expects in their inbox.

The task cancellation half is real and good advice - start it in your app entry point and hold it for the process lifetime, never inside a view.

There is no background wake for renewals though. If the app is not running, nothing is delivered until it next runs, which is precisely why the server notification endpoint exists. Half right is unhelpful here because it sends OP looking at their task lifecycle for a problem that is not there.

The limits block covers CPU time, not heap. Worker memory is fixed and is not something you can buy more of on that runtime. If you genuinely need memory you need different compute - a container, a VM, anything with a knob. Sending OP off to edit a config that has no effect is a bad two hours out of the twelve days they have left.

The previews thing is such a small change for how much of the day it seems to affect. Trying it today.

Did the hot percarbonate wash last night and the water was genuinely grey, which was horrifying. They're fine today.

The filter had a hair tie, two coins and something I've chosen not to identify. Cleaned.

Pulled 90 for 5 with straps and my back felt like it did the work for the first time in weeks.

Twenty second unlisted video of the whole app in the notes. If your entire app fits in twenty seconds, that is a superpower, use it.

There is one and I assumed it was just lighter. Trying it on Thursday.

One box means one restart takes everything down anyway. Adding Redis there does not buy availability, it buys a second daemon competing for 2 GB of RAM behind the same single point of failure.